Hello Mike & Dave, Thanks for your inputs here. But basically there are no other monitoring that is on which can consume much of alarm resources. My snmpd daemon here is running as a SUb agent and not as masteragent and it has only agentx Masteragent's socket defned in conf file nothing else.
For a sub agent for what purpose run_alarm's needed here, and why this shoudl contribute the CPU time. Let me know. Thanks & Regards, Bheemesh On Wed, Dec 9, 2009 at 1:54 AM, Dave Shield <d.t.shi...@liverpool.ac.uk>wrote: > 2009/12/8 Mike Ayers <mike_ay...@tvworks.com>: > > Check your snmpd.conf file. I suspect you've got a lot of > > monitoring turned on. Many of the monitors: disman, RMON, > > hardware monitoring, etc. use alarms to schedule their activity, it would > seem. > > There are also some MIB modules which rely on re-loading the data > on a regular basis - either to ensure up-to-date information (particularly > if it's relatively timeconsuming to load on demand), or to calculate > rolling average metrics (e.g. various CPU statistics) > > Dave >
------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
_______________________________________________ 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
