While investigating the engineID problem caused by using -C with -c, i
discovered that optional config files are processed last, and processes PREMIB
and NORMAL config at the same time. It seems to me that this will cause
problems for tokens which might expect that all PREMIB tokens will be dealt
with before all NORMAL tokens.
That's easy enough to fix (see my patch attached to patch 1217475), but it
started me thinking. It might be desirable, sometimes, to have the optional
config file processed before the default config files. We've used '+' as a
special symbol before, so it wouldn't be a big stretch to imagine that
snmpd -c +/home/bob/my.conf
would cause my.conf to be processed before the default config files.
Any thoughts? Objections?
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
