Ahh ''mib2c -c mib2c.notify.conf' would seem to be the magic charm I'm seeking.
Much appreciated, Garyc ----- Original Message ----- From: "Dave Shield" <[EMAIL PROTECTED]> To: "Gary Clark" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 20, 2004 8:54 AM Subject: Re: trap question > > > I have just found an example. > > > > In /net-snmp/agent/mibgroup/example/notification.c > > > > I will use this code if thats Ok? > > Yup - that's a reasonable place to start. > Another is to run > 'mib2c -c mib2c.notify.conf' > on your MIB. > > But both of these are primarily concerned with *how* to generate > the trap, rather than *when*. The 'example/notification.c' code > will generate this trap every 30 seconds, the mib2c output doesn't > itself generate any trap at all. > > But they both provide a routine that you can invoke whenever > it's appropriate to send a trap. But it's up to *you* to work > out when to call this routine - perhaps in a signal handler, > or following a regular check if anything has changed. > > Dave ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
