Hi everyone, I seem to have a little problem. I have several Net-SNMP v5.3.0.1 clients on various Solaris servers, and I get the following trap from several of them:
mteTriggerFired trap received from xxxxxxxxxxxxxxxxx: procTable .1.3.6.1.4.1.2021.2.1.100.2 1 cron This does NOT appear to be an error. I'm used to seeing procTable errors in the form of: mteTriggerFired trap received from xxxxxxxxxxxxxxxxx: procTable .1.3.6.1.4.1.2021.2.1.100.19 1 wots Too few wots running (# = 0) Here's a typical snmpd.conf proc section: proc automountd 1 1 proc cron 1 1 proc devfsadm 1 1 proc fsflush 1 1 proc inetd 1 1 proc lcfd 1 1 proc mountd 1 1 proc nfsd 100 1 proc nmbd 1 1 proc nscd 1 1 proc prngd 1 1 proc rpcbind 1 1 proc sac 1 1 proc smbd 100 1 proc sshd 100 1 proc syseventd 1 1 proc syslogd 1 1 proc utmpd 1 1 proc vxconfigd 1 1 proc vxnotify 1 1 proc vxrelocd 3 1 proc wots 1 1 proc xntpd 1 1 Any idea why Net-SNMP would send a trap for cron? Thanks, js. -- Jean-Sebastien Morisset, Sr. UNIX Administrator <[EMAIL PROTECTED]> Personal Home Page <http://jsmoriss.mvlan.net/> Underwater and Travel Photographs <http://www.mvpix.com/> ------------------------------------------------------- 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