> > Note that there has been a problem with the last couple
> > of releases (including the 5.4.1.preX tarballs), which may
> > possibly result in the Workspace files having the wrong
> > line endings. This means that Visual Studio doesn't
> > always recognise them as such.
> >
> Maybe Microsoft ha
-Original Message-
From: "Dave Shield" <[EMAIL PROTECTED]>
To: "Aleksandr Lomanov" <[EMAIL PROTECTED]>
Date: Sat, 23 Jun 2007 16:27:25 +0100
Subject: Re: visual c++
> Note that there has been a problem with the last couple
> of releases (including the 5.4.1.preX tarballs), which may
> pos
kjonze wrote:
> I am using net-snmp 5.4 to send v3 informs to a utility using the -C i
> parameter but they are being transmitted on port 161. How do I adjust
> it so
> that it gets sent on port 162?
The upcoming 5.4.1 release (currently at pre3) will fix this.
In the meantime, you may want to
All,
I am using net-snmp 5.4 to send v3 informs to a utility using the -C i
parameter but they are being transmitted on port 161. How do I adjust it so
that it gets sent on port 162?
-
This SF.net email is sponsored by DB2 E
On 23/06/07, Alex Burger <[EMAIL PROTECTED]> wrote:
> Aleksandr Lomanov wrote:
> > visual c++ workspace no more supported ?
> > When it will be supported ?
> >
> It's still supported. What makes you think it isn't?
Note that there has been a problem with the last couple
of releases (including th
Aleksandr Lomanov wrote:
> visual c++ workspace no more supported ?
> When it will be supported ?
>
It's still supported. What makes you think it isn't?
Alex
-
This SF.net email is sponsored by DB2 Express
Download DB2 E
On 22/06/07, Sukwoo Kang <[EMAIL PROTECTED]> wrote:
> A. Make 2 (libnetsnmpagent.so) be linked with 3 (libnetsnmphelpers.so). It
> requires the second-pass build.
That is the intention for 5.5 and above - these two libraries are due to be
merged into one. But that's too biga change to introd
