Question about persistent community names

This one caught me off guard.  Please, if somebody can explain what is
happening please let me know.

This afternoon I found a server that had an old community string
configured in the /etc/snmpd.conf file.  (This is a SUSE Linux server.)
I commented out the old community line and added a new one with a
hostname parameter.  Here is what the final config looked like
(fragment):

# rocommunity <old community>

rocommunity <new community> <hostname>

After that I bounced the snmpd daemon (as root):

/etc/init.d/snmpd stop
/etc/init.d/snmpd start

Now BOTH community names are enabled!  I can do an snmpwalk on either of
them.  This must be a rookie mistake, but I assumed the old community
string would be removed from the config.  Can anyone explain where the
old community name is coming from and how I can get rid of it?  I'd
rather not use the '-C' parameter since I could lose information in the
persistent cache.  But if that's the only way then let me know.

Walker Archer <[email protected]>
Edison Systems Management
(313) 845-1147

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
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