Also, if you remove the configuration entry, it doesn't work either. -----Original Message----- From: Fong Tsui Sent: Wednesday, November 21, 2007 12:12 PM To: Fong Tsui; '[email protected]' Subject: RE: SIGHUP
I found that it doesn't work if you add the comments in front of the configuration entry. But if you really change the configuration entry, it works fine. -----Original Message----- From: Fong Tsui Sent: Wednesday, November 21, 2007 12:06 PM To: [email protected] Subject: SIGHUP Hi, everybody, I am trying to use "SIGUP" to re-load the configuration instead of restarting snmpd. It seems some of configuration is reloaded correctly but some of them are not. When I comment out rocommunity entry in snmpd.conf and do "killall -HUP snmpd", I can see log message: snmpd[6458]: Warning: no access control information configured. It's unlikely this agent can serve any useful purpose in this state. Run "snmpconf -g basic_setup" to help you configure the snmpd.conf file for this agent. The above message indicates the configuration is changed but I still can access the snmpd. If I restart snmpd, then I am not able to access snmpd as it is configured. Is there a bug for this already? Thanks, FT ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
