On 20/07/06, vic <[EMAIL PROTECTED]> wrote:
> At present, I still do not know where I
> went wrong. ...
> Any ideas I can start with?
Well, there are basically two likely sources for this problem:
a) The agent doesn't include support for these two tables
b) The agent does, but the snmpd.conf file doesn't
You could check the first possibility by:
- walking the nsMibRegistry table, and looking for the dskTable or
procTable OIDs
- running 'nm' on libnetsnmpmibs, and looking for var_extensible_{disk,proc}()
- "make clean ; make' in the source, and check whether disk.o or
proc.o are created
You could check the second by running 'snmpd -f -Le -Dread_config' and
looking for the relevant config entries being parsed.
There's a theoretical third possibility, I suppose - a bug in the
agent - but that seems rather unlikely :-) But seriously, I don't
think this code has been touched in years, so I'd be surprised if we'd
introduced any problems that *just* hit these two modules.
If pressed, my guess as to the most likely cause would be that the
agent is reading a different config file to the one you expect.
-Dread_config should reveal if that's the case.
A few idea to get you started, anyway.
Dave
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
