Dean wrote:
We had a situation recently where a hard NFS mount suddenly became
unavailable (it was taken away without unmounting, I know, yuck).
After which found that the snmpd process was consuming 3.2% (which on
this particular host is 1 full CPU in a 32-CPU 69k - Solaris 9). Further
investigation revealed that the process is spending 100% of its time in
system
[...]
I'm just wondering if this is expected behaviour of snmpd, in a
situation where an NFS mount becomes unavailable.
Unfortunately there's not much we can do about this. A hard mount means
exactly this: system calls to access this filesystem *block* if it's not
available instead of returning an error. This is what you're seeing here.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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
