RE: A SIGHUP signal just kills snmpd daemon instead of reloading theconfig.

kill -hup pid, where pid = the snmpd process id.
 
worked when I tried it.


________________________________

From: [email protected]
[mailto:[email protected]] On Behalf Of Hu,
Fengliang
Sent: Friday, August 01, 2008 5:29 PM
To: [email protected]
Subject: A SIGHUP signal just kills snmpd daemon instead of reloading
theconfig.


Hi,
 
This is Feng. I am poking net-snmp software 5.4 on x86 Linux (ubuntu
7.4) and trying to see how it can reloads the new configuration (such as
the updated community string). Googled some articles, I thought SIGHUP
signal needs to be sent to snmpd process. I also took a look at the code
and it seems that on Linux it installs the signal handler for SIGHUP to
set a reconfig flag. But for me, snmpd always simply died after I "kill
-s SIGHUP <snmpd_pid>".
 
Snmpd was started with the following command line options:
"
-u 0 -Ls5 -Lf /dev/null -p <PID_FILE_FULL_PATH> -c
<SNMP_CONFIG_FILE_FULL_PATH> -M <MIB_DIRS>"
"
 
Thanks for any feedback here.
Feng

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
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