On tor, 2007-07-05 at 15:28 +0300, Juuso Alasuutari wrote:
> On Sunday 24 June 2007 23:21:46 Magnus Fromreide wrote:
> > On sön, 2007-06-24 at 14:14 +0200, Thomas Anders wrote:
> > > Juuso Alasuutari wrote:
> > > > The distribution is Debian unstable, libsnmp version is 5.3.1, and
> > > > Valgrind
On Sunday 24 June 2007 23:21:46 Magnus Fromreide wrote:
> On sön, 2007-06-24 at 14:14 +0200, Thomas Anders wrote:
> > Juuso Alasuutari wrote:
> > > The distribution is Debian unstable, libsnmp version is 5.3.1, and
> > > Valgrind is 3.2.3. Is this kind of behavior normal from libsnmp, or is
> > > t
On Sunday 24 June 2007 23:21:46 Magnus Fromreide wrote:
> On sön, 2007-06-24 at 14:14 +0200, Thomas Anders wrote:
> > Juuso Alasuutari wrote:
> > > The distribution is Debian unstable, libsnmp version is 5.3.1, and
> > > Valgrind is 3.2.3. Is this kind of behavior normal from libsnmp, or is
> > > t
On Monday 25 June 2007 16:30:28 Dave Shield wrote:
> OK - can you please try the following:
>
>a) Replace the directive "exec truth /bin/true"
> with "sh truth /tmp/true"
>
>b) Create a shell script /tmp/true
> containing
>
> #!/bin/sh
>
On 25/06/07, Juuso Alasuutari <[EMAIL PROTECTED]> wrote:
> I did as you suggested and left only the 'rocommunity public' line in
> snmpd.conf, but I still get the freeze.
Hmmm...
OK - can you please try the following:
a) Replace the directive "exec truth /bin/true"
with "sh
On Monday 25 June 2007 14:23:08 Dave Shield wrote:
> On 25/06/07, Juuso Alasuutari <[EMAIL PROTECTED]> wrote:
> > Here's my snmpd.conf:
> > rocommunity public
> > com2sec paranoid default public
> > com2sec readonly default public
>
> Well, the first thing that springs out is that
On 25/06/07, Juuso Alasuutari <[EMAIL PROTECTED]> wrote:
> Here's my snmpd.conf:
> rocommunity public
> com2sec paranoid default public
> com2sec readonly default public
Well, the first thing that springs out is that you've got three
inconsistent settings here.
Either the com
On Sunday 24 June 2007 22:04:16 Juuso Alasuutari wrote:
> On Sunday 24 June 2007 15:14:01 Thomas Anders wrote:
> > Would you mind building net-snmp 5.4.1.pre3 from source, compile the
> > test program against it and re-run your test?
>
> Not at all. I built and installed the prerelease with
> `./co
On sön, 2007-06-24 at 14:14 +0200, Thomas Anders wrote:
> Juuso Alasuutari wrote:
> > The distribution is Debian unstable, libsnmp version is 5.3.1, and Valgrind
> > is
> > 3.2.3. Is this kind of behavior normal from libsnmp, or is the test
> > program's
> > code broken in some way?
>
> Would
On Sunday 24 June 2007 15:14:01 Thomas Anders wrote:
> Juuso Alasuutari wrote:
> > The distribution is Debian unstable, libsnmp version is 5.3.1, and
> > Valgrind is 3.2.3. Is this kind of behavior normal from libsnmp, or is
> > the test program's code broken in some way?
>
> Would you mind buildin
Juuso Alasuutari wrote:
> The distribution is Debian unstable, libsnmp version is 5.3.1, and Valgrind
> is
> 3.2.3. Is this kind of behavior normal from libsnmp, or is the test program's
> code broken in some way?
Would you mind building net-snmp 5.4.1.pre3 from source, compile the
test program
Hi.
I'm learning how to write a monitoring client using libsnmp. I copied from the
example application in the wiki
(http://www.net-snmp.org/wiki/index.php/TUT:Simple_Application) and wrote a
small test program which performs an SNMPv1 query. I ran it with valgrind and
got 23 errors from 18 con
12 matches
Mail list logo