On 15 May 2012 15:56, Gary Dunlap <gary.dun...@dothill.com> wrote: > To paraphrase this, and Suresh's original message, are you saying that > sending a SIGHUP signal to re-read the .conf file is no longer supported > for SNMPv3 users definitions? "No longer" meaning version 5.7.1.
I am not aware of any recent changes to the code that would affect the behaviour of re-reading config files. There wasn't a great deal of detail in Suresh's original message as to exactly what he was doing - so I'm relying on guesswork a bit here. But my suspicion is that he was editing the persistent config file (while the agent was running) to add a new SNMPv3 user, and then sending the agent a HUP signal. On receipt of that signal, the agent would flush its internal configuration to the persistent config file (thus overwriting the changes) and re-load all of the config files. I'd need to do some testing to be certain, but I suspect that adding SNMPv3 users or making changes to config files *other* than /var/net-snmp/snmpd.conf should work OK with HUP. It's just editing the persistent config file while the agent is running that's likely to cause problems. But all of this is educated guesswork, and I could easily be wrong! Dave ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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
