Re: rfc: snmptrapd as sub-agent

Getting back to the original issue:

On Mon, 2005-06-13 at 23:12, Robert Story wrote:
> We've had some people with memory problems with snmptrapd, which seem
> to be (at least partially) because of the new sub-agent code that
> implements the notificaiton log mib. Unfortunately, there is no way
> to configure snmptrapd to not be a sub-agent. I think this is a bug.

I'm not sure that I'd categorise this as a bug. But there should
definitely be some way to configure the trap daemon to run standalone.

a) At run time (don't initialise the AgentX code)
b) At compile time (don't include the AgentX code at all)

Where b) is a separate decision from whether AgentX support is included
in the agent libraries (though this would obviously be pre-requisite)


> probably makes sense to have a cmd line flag and a conf file token.

Agreed.
Plus a "configure" option to disable this from the build completely.


> The current default is on. I think, like the master agent,
> it should be off

Ummm....
Not sure. My gut reaction is to keep things as they are by default,
and just add the flexibility to exclude this facility. But changing
the default later is easy - the first thing is to get the configuration
mechanisms in place.

Dave



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders