On Wed, 13 Oct 2004 07:09:44 +0930 don wrote: DH> > Not presently, but there are two interesting idea there. One (sending to DH> > multiple ip addresses from the command line) has been brought up before. DH> > The other, using a conf file, is new. I'm not sure that reading DH> > snmpd.conf would be a good idea, but reading a snmptrap.conf that DH> > specifies trap destinations is an interesting idea. You might wnat to DH> > submit those as feature requests (or code them up and submit a patch). DH> DH> Hmm. I had thought that snmpd.conf would be a good file to read, since DH> that already specifies trap destinations for traps sent out using DH> library calls from the agent/subagent.
Right, but not everyone who uses snmptrap is acting on behalf of an agent. What you may not realize is that if snmptrap were to suddenly start reading snmpd.conf, every user would be parsing the system snmpd.conf, possibly sending traps somewhere they didn't intend to. DH> Is there any functionality to DH> be gained by repeating these definitions in a different configuration DH> file (snmptrap.conf)? It's flexibility. I think it is more likely that a user will want to send traps to a different location than the agent would. DH> Given the current 'all or nothing' approach to traps (using the DH> library calls, a trap is sent to all destinations configured in the DH> snmpd.conf file, You are overgeneralizing. The library sends traps to destinations in the trap-sink list. It also calls a callback, which the agent registers to use the notification table. The library knows nothing of what conf file was parsed to get the configuration. DH> it seems a logical extension to say that the DH> destinations configured in the configuration file used by the agent DH> for sending traps are necessarily the same as those used for sending DH> traps using snmptrap. Or maybe that's an unnecessary restriction? snmptrap is it's own application, and as such, should read it's own configuration. And idea that just popped into my head, though, would be an option to snmptrap to have an option to register as an AgentX sub-agent, and then send the traps via the master agent. Then they would be sent to all the locations configured in the agent. DH> with filters as the only way to select a subset of DH> destinations, correct?), Theoretically, but that doens't actually work yet. It will probably be in 5.3, with a slight chance that it might make it into one of the 5.2 point releases. DH> Perhaps a new snmptrap.conf, which is somehow 'included' or read by DH> the agent, so the information can be removed from snmpd.conf directly? Again, you are thinking of snmptrap.conf in terms of functionality. However, conf files are based on the application name. -- Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- 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
