Re: 5.3.1.pre3 released

2006-06-03 Thread G. S. Marzot
Thomas Anders wrote: > G. S. Marzot wrote: >> retest with pre3... >> >> similar issues. > > The three failures from this run seem to be due the following: > > - #19 (T030snmpv3usercreation) failure: agent in the second run > (persistence check) doesn't start up properly (i.e. never writes > "NET-

Re: 5.3.1.pre3 released

2006-06-03 Thread Thomas Anders
G. S. Marzot wrote: > retest with pre3... > > similar issues. The three failures from this run seem to be due the following: - #19 (T030snmpv3usercreation) failure: agent in the second run (persistence check) doesn't start up properly (i.e. never writes "NET-SNMP version" into the logfile) - #

Re: HPUX 11.11 PS_RISC1.1

2006-06-03 Thread Thomas Anders
Johannes Schmidt-Fischer wrote: > What sort of problems do you have exactly? Indeed, it's hard to fix build issues without seeing the exact error messages. :-/ Does a bare "./configure --with-defaults && make" build fine for you with 5.3.1.pre3? What does "perl -V" reports for your Active Stat

Re: core dump in netsnmp_check_outstanding_agent_requests

2006-06-03 Thread Thomas Anders
Fong Tsui wrote: > I am running into a core dump in > netsnmp_check_outstanding_agent_requests(). > It is v5.0.9 and on Linux. The 5.0.x branch is about to be EOLed. Can you reproduce this with 5.0.11.rc1? Updating to a current branch (5.3.1.pre3 etc.) is recommended. +Thomas ___

Re: HPUX 11.11 PS_RISC1.1

2006-06-03 Thread Johannes Schmidt-Fischer
Hello Michael, for compilation with HP-UX 11i I'm using HP's own cc (AnsiC), but I presume that it should work with gcc as well. Probably you've seen the thread "5.3.1.pre2 build test status" in the net-snmp-coders mailing list, where Thomas Anders stated that compilation für e.g. HP-UX 11i (11.11

[no subject]

2006-06-03 Thread Anurag Verma
Currently we have two different management interfaces - CLI and SNMP. The managed data is stored in our backend code that is common to both CLI and SNMP. However, I would not like to expose my managed data directly to the SNMP subagent. So, we have an API exposed to the SNMP. In this context,