RE: New front end for the Net-SNMP website.

2004-12-27 Thread atonns
Title: RE: New front end for the Net-SNMP website. The new design for the website looks great. Access to the MIB docs and man pages are much more straightforward. I particularly liked readying the History section - a lot of stuff in there I didn't know about the project. However... What happe

RE: same problems with "extend" as with "exec"

2004-10-27 Thread atonns
Title: RE: same problems with "extend" as with "exec" I've run a few quick tests, and it looks like this patch works great. I'll leave it running and see how it does. Will it make it into the 5.2 final release? Thanks, Tony -- "Replicants are like any other machine, they're either a benefi

same problems with "extend" as with "exec"

2004-10-27 Thread atonns
Title: same problems with "extend" as with "exec" In trying out the new NET-SNMP-EXTEND-MIB (ie: the "extend" config option in snmpd.conf), I'm having similar problems to those I had with "exec" in version 5.1.x. Using the following command: snmpwalk localhost NET-SNMP-EXTEND-MIB::nsExtendOut

anti-whining

2004-10-20 Thread atonns
Title: anti-whining > Now if you'd like to discuss paid support, then that's > another matter. Until > then, no whining please. I was recently pleasantly surprised when I got an email about a fix for a bug that I filed on SF.net. I had reported it months ago, and thought that it went unsolv

RE: Interface state on Solaris 8 for bgeX interfaces

2004-09-23 Thread atonns
Title: RE: Interface state on Solaris 8 for bgeX interfaces For comparison, I do not have this problem with net-snmp 5.0.9 on Solaris 9: prodws2$ ifconfig -a lo0: flags=1000849 mtu 8232 index 1     inet 127.0.0.1 netmask ff00 bge0: flags=1000843 mtu 1500 index 2     inet 192.168.

RE: agent hung up running "exec" process

2004-08-03 Thread atonns
Title: RE: agent hung up running "exec" process My apologies... here's my reply in plain text. stupid corporate email standards -- "Computer science is as much about computers as     astronomy is about telescopes" -- Edsger Dijkstra -

RE: agent hung up running "exec" process

2004-08-03 Thread atonns
Bruce, One last point on the relevance of these MIBs - There's a 'secret' feature built into memconf (http://www.4schmidts.com/memconf.html) where if you take the output of "prtdiag -v" and "prtconf -pv" and 'cat' them together into one file, you can then "memconf -v combinedoutput.txt". This wil

RE: agent hung up running "exec" process

2004-08-03 Thread atonns
Title: RE: agent hung up running "exec" process > From: Dave Shield [mailto:[EMAIL PROTECTED]] > >   The first thing that I'd be inclined to check is whether > this problem > is triggered by the output that's being read in (perhaps the > size of it), > or whether it's connected to the comm

RE: agent hung up running "exec" process

2004-08-02 Thread atonns
Update: I tested this on 5.1.2.rc2 with the same result as 5.1.1 - truncated command output and a hanging of the agent on the one MIB (prtconf). Going backwards instead of forwards - the 3 MIBs listed below work without any problems in version 5.0.9. Same exact "configure" command line, only the

missing libs?

2004-08-02 Thread atonns
Title: missing libs? I'm attempting to compile net-snmp-5.1.2.rc2 on Solaris 9 4/04. I get this from configure: checking netinet/tcpip.h usability... no checking netinet/tcpip.h presence... yes configure: WARNING: netinet/tcpip.h: present but cannot be compiled configure: WARNING: netinet/tc

RE: agent hung up running "exec" process

2004-07-28 Thread atonns
I can agree with your point - that these can be expensive to query. However... 1) I only query the prtdiag/prtconf MIBs once a day for automated inventory (and VERY occassionally manually), so it's really not THAT expensive. I'm looking at the idprom, etc. 2) With the "ps" command, the hrSWRunTab

RE: agent hung up running "exec" process

2004-07-28 Thread atonns
Actually, I've tried adding the -t option with 30, 60 and even 90. Still nothing. I've checked a few more of the "exec" lines that I have in my snmpd.conf and it looks like the output from them is being truncated at around 25 or 30 lines. They originally all looked like this: exec .1.3.6.1.4.1.202