Dave> [status persistent] Dave> sysLocation Sitting in the workshop, waiting to be fixed Dave> repairTimeEstimate You must be joking, squire! Wes> This is impossible to realize in a safe manner. It would require Wes> applications to edit configuration files on the fly, which is both Wes> code-error prone or resource error-prone (eg, full disks).
But we *already* do that with the /var/net-snmp/ files. And we've already got this facility with the "psys*" directives. I'm just talking about applying the same approach in a more consistant manner - i.e. within a comprehensive configure framework, rather than ad-hoc for individual directives. Wes> We should only modify files explicitly persistent in nature, I never proposed doing anything else! A directive marked as "persistent" would be first read from the 'static' config file and the value then overridden (or augmented) by the settings from any /var/net-snmp/ files. And on agent shut-down, the current value(s) would be saved to the /var/net-snmp/ file, leaving the original untouched. Exactly as we do with 'psys*' at the moment. Dave ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
