Wes> How about:
Wes> host=*.example.com defCommunity public
Wes> We have no tokens that have a = sign in them to date...
*We* don't, no - but can you guarantee that nobody else has?
Is this syntax explicitly forbidden in either the documentation
or the config token parsing code?
(Open question - I haven't looked)
As a general rule, I'd prefer a "blocked" syntax over a "per-line" one.
I can foresee having to repeat host-specific over several related lines
and
host=*.example.com this that theother
host=*.example.com bish bash bosh
host=*.example.com veni vidi vici
<etc, etc>
could start to get cumbersome very quickly.
Wes> I liked option 3 from the original proposal:
Wes> <host> ...
Wes> We could, of course, over engineer it...
Wes> <filter type=host value="*.example.com"> defCommunity ick
I'd suggest that we don't adopt an XML-style syntax unless we
intend to go the whole hog. Although I'm not a great fan of
XML-based configuration, it *is* a perfectly valid approach,
and I can envisage us wanting to investigate this possibility
some time in the future. It would be unwise to block that option
off now.
The other idea to throw into the melting pot is one that John
came up with a couple of years ago - being able to mark configuration
blocks as being "fixed" (i.e. read-only), "transient" (changes are
discarded on reboot) or "persistent" (i.e. saved to /var/...)
At the moment, we've got a fairly ad-hoc mechanism using distinct
config directives (syslocation vs psyslocation). It would be much
more useful to be able to denote this in a standardised manner.
For example, extending Alex's idea slightly
[status fixed]
sysContact Me...
[status persistent]
sysLocation Sitting in the workshop, waiting to be fixed
repairTimeEstimate You must be joking, squire!
[status transient]
sysServices 0
The syntax is just for illustration, I hasten to add - it's the
basic concept I'm more interested in at the moment.
Dave
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------------------------------------------------
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
