-Config file defined by SNMP_PERSISTENT_FILE is now backed up and purged before writing so it doesn't continiously grow. Previously, the file would keep getting bigger and bigger. Actually, it wasn't even being backed up at all as the backup code didn't check for SNMP_PERSISTENT_FILE. Note: It does not currently load the backed up config files when SNMP_PERSISTENT_FILE is used. I'm out of time, so I'll look at it on Monday.
None of the SNMP_PERSISTENT_FILE problems above exist if the name of the file specified is snmpd.conf. This isn't documented anywhere (neither is SNMP_PERSISTENT_FILE). It should either be documented, or fixed like above. Documenting *is* much easier of course.
Right now only snmpd uses the persistent storage. If another application uses it in the future, would we want to use SNMP_PERSISTENT_FILE? Using snmp.conf persistentDir, SNMP_PERSISTENT_DIR or the compiled in PERSISTENT_DIRECTORY uses the application name in the filename. Is SNMP_PERSISTENT_FILE used by many people?
Alex
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
