On 2 Nov 2006 05:49:50 -0000, joseph antony
> What ever SIGNAL it may be say SIGKILL or SIGTERM or HUP the
> behaviour is same.

I'm surprised.
The expected behaviour of KILL, TERM and HUP is very different.

HUP ought to signal the agent to re-read the config file, while
continuing to run.
TERM should signal the agent to shut down gracefully, saving any internal state.
KILL should tell the agent to quit as fast as possible - & not to bother saving
any internal information.

Don't use "kill -9" - this may well leave the configuration in an
inconsistent state.
Always use "kill {pid}" if you want to shut the agent down.

If your'e still seeing the same problems, can you try the following:

- Move *all* configuration files out of the way (or delete them)
- create a file /var/net-snmp/snmpd.conf containing *just* the
"createUser" line
- start the agent using "snmpd -f -Le -Dread_config"
- from a separate window, send the agent the TERM signal

Q1: What is the full output from "snmpd" ?
Q2: What are the new contents of /var/net-snmp/snmpd.conf ?

- now add the "trapsess" line into the /usr/local/share/snmp/snmpd.conf file
- start the agent using "snmpd -f -Le -Dread_config"
- from a separate window, send the agent the TERM signal

Q3: What is the full output from "snmpd" ?
Q4: What are the contents of /var/net-snmp/snmpd.conf ?


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Net-snmp-users mailing list
Please see the following page to unsubscribe or change other options: