Re: On the opening of sockets

2005-09-09 Thread Magnus Fromreide
On Fri, Sep 09, 2005 at 09:39:20AM +0100, Dave Shield wrote: > On Thu, 2005-09-08 at 19:12 +0200, Magnus Fromreide wrote: > > On Thu, Sep 08, 2005 at 02:52:35PM +0100, Dave Shield wrote: > > > > In fact, it might be sensible for the OSI and Appletalk > > > transport-specific parsing code to check

Re: CVS MAIN broken

2005-09-09 Thread Thomas Anders
Robert Story wrote: I just did a fresh checkout to a new directory, then ./configure --with-defaults --enable-mfd-rewrites make make test and got Summary: 46 / 46 succeeded. Me, too! :o Strange. Dave, what about you? +Thomas -- Thomas Anders (thomas.anders

Code versioning scheme

2005-09-09 Thread Lisa Morgan
I looked at net-snmp.org but couldn't find a description of your code versioning scheme -- e.g. 5.0.10.2. What causes the various numbers to be incremented? _ Lisa A. Morgan IBM Printing Systems T/L 263-5059 303-924-5059 --- S

Re: SNMP v3 Not Thread Safe even using Single Session API

2005-09-09 Thread John McCaskey
Ugh... the situation is what I feared :) See comments inline...On 9/9/05, Dave Shield <[EMAIL PROTECTED] > wrote:On Thu, 2005-09-08 at 09:15 -0700, John McCaskey wrote:> I was under the impression from reading > http://www.net-snmp.org/docs/README.thread.html that as long as I> stuck to the Single

Re: MFD_SKIP confusion

2005-09-09 Thread Tom Cumming
Robert Story wrote: On Fri, 09 Sep 2005 09:44:50 -0700 Tom wrote: TC> Where did I got wrong? The code is right, so you've hit a bug somewhere. I'm surprised. I assumed that there were a lot of people using this code in the same manner I am, so if there were any bugs, someone would have h

Re: CVS MAIN broken

2005-09-09 Thread Robert Story
On Fri, 09 Sep 2005 00:20:16 +0200 Thomas wrote: TA> Robert Story wrote: TA> > On Wed, 07 Sep 2005 12:11:29 +0100 Dave wrote: TA> > DS> On Wed, 2005-09-07 at 12:52 +0200, Thomas Anders wrote: TA> > DS> > CVS MAIN is broken for me (on Linux/x86). "make test" fails, TA> > DS> > because the agent cras

Re: Regarding hrStorageTable

2005-09-09 Thread Robert Story
On Fri, 09 Sep 2005 10:09:21 +0530 Naganarasimha wrote: N> The mibs which come under"iso.org.dod.internet.mgmt.mib-2" should it be N> available irrespective of any OS? No. It's entirely up to the agent device. There are some standard mibs that are 'required' to claim full compliance with the

Re: MFD_SKIP confusion

2005-09-09 Thread Robert Story
On Fri, 09 Sep 2005 09:44:50 -0700 Tom wrote: TC> I believe I'm confused on the use of MFD_SKIP. We have a table and TC> used mib2c -c mib2c.mfd.conf to build our skeleton code. I haven't TC> implemented one of our objects yet, so I just wanted return MFD_SKIP, to TC> get snmpwalk to, "skip" ove

MFD_SKIP confusion

2005-09-09 Thread Tom Cumming
I believe I'm confused on the use of MFD_SKIP. We have a table and used mib2c -c mib2c.mfd.conf to build our skeleton code. I haven't implemented one of our objects yet, so I just wanted return MFD_SKIP, to get snmpwalk to, "skip" over it. Here's a code snippet: /** * Extract the current value

Re: Are the debug tokens categorised???

2005-09-09 Thread Dave Shield
On Fri, 2005-09-09 at 00:45 +0200, Thomas Anders wrote: > Dave Shield wrote on 2004-08-23(!): > > Dave> But one of the major tasks is to go through the existing debug > > statements > > Dave> and come up with a suitable hierarchical debug token structure. > > Dave> (Plus identifying where we reall

Re: SNMP v3 Not Thread Safe even using Single Session API

2005-09-09 Thread Dave Shield
On Thu, 2005-09-08 at 09:15 -0700, John McCaskey wrote: > I was under the impression from reading > http://www.net-snmp.org/docs/README.thread.html that as long as I > stuck to the Single Session API for forming and sending requests I > would be ok. However, it appears that while this is true for

Re: On the opening of sockets

2005-09-09 Thread Dave Shield
On Thu, 2005-09-08 at 19:12 +0200, Magnus Fromreide wrote: > On Thu, Sep 08, 2005 at 02:52:35PM +0100, Dave Shield wrote: > > In fact, it might be sensible for the OSI and Appletalk > > transport-specific parsing code to check for these common > > port numbers, and convert them into the equivalent