On Thu, 2006-03-02 at 09:38 -0500, Jean-Sebastien Morisset wrote: > I was able to reproduce the problem. I copied a few gigs on the > filesystem and then removed it. Right after, I ran an snmpwalk. It stuck > for second half way through, and then gave me the following:
> dskTotal.2 = INTEGER: 142436675 > dskAvail.2 = INTEGER: 140139526 > dskUsed.2 = INTEGER: -2147483648 Urk! > dskErrorFlag.2 = INTEGER: 1 Well that would certainly explain why the monitor entry is being triggered :-) OK - so the problem lies with the disk table. Unfortunately, that code isn't particularly clean. (I've got plans, but not enough time). What O/S is this running on? Dave ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ 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
