On Wed, 2005-05-04 at 16:07, Alex Burger wrote: I can see the thinking behind this approach, but I'm not convinced that it's correct. In particular, someone might well be deliberately using SNMPCONFPATH in order to avoid loading the "normal" config files.
It would probably be more in keeping with the project style to use a syntax such as
SNMPCONFPATH=+/some/directories/to:/add/to:/default/list vs SNMPCONFPATH=/some/directories/to:/replace:/default/list
Though I realise that still leaves open the question of the status
of the persistent directory,
Thomas Anders wrote: > Do *not* check this in, please. This'd be an incompatible change in > behaviour that would at least break all of *my* uses of SNMPCONFPATH.
I wanted to check to see if this is normal behaviour, or a bug that was introduced at some time. It sounds like it's normal behaviour.
An option would be if SNMPCONFPATH is defined, to only use that path PLUS the persistent path. Is there ever a time when one would NOT want to use the files in the persistent folder? My understanding is that the persist folder is used by snmpd internally, except for the createUser token.
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
