>>>>> On Fri, 06 Feb 2009 09:58:00 -0700, Tushar Gohad <tgo...@mvista.com> said:

TG> My question is: were the 'release' routines left out intentionally,
TG> say to avoid cleaning out someone else's (subagent, command line
TG> trap addition etc) monitor entries?  Or is there a safe way to clean
TG> the entries out?

They were left out simply because they weren't finished.  We'd happily
accept a patch to create the appropriate release routines :-)

TG> Most of the 'monitor' entries seem to be created with owner
TG> 'snmpd.conf.'

The Table requires some sort of owner name.  We could make that
configurable, you're right, but "snmpd.conf" seemed simple and easy and
making it configurable to something else didn't seem worth the effort
since it would be of little use.

TG> Is there any other way to distinguish the entries as being owned by
TG> the process that the SIGHUP is sent to?

I understand what that question is trying to ask...



In the future, please don't write personal messages to people asking for
help...  You have to be patient with the mailing lists as people are
busy and get to the list when they get the time as open source projects
are often supported by people on their own time.  The people that
contribute answers get to an answer when we have time to respond to
questions on the list.

-- 
Wes Hardaker
Sparta, Inc.

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
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

Reply via email to