> But my overall assumption is that we stick what we currently have, but > extend > it in a way that provides scoping and do so in a way the provides as > many > usable interim steps as possible (without adding major work just for > those > steps). I hope this covers the spirit of our discussion.
I tried very hard the past days to get a grammar together that is an evolution from what we currently have. I did not yet succeed fully (thus I have no formal grammar to show), but I think I made some progress. So please let me come back and present a config sample: http://download.rsyslog.com/rainerscript2_rsyslog.conf It actually is three configs in one file a) a standard rsyslog.conf in mixed new and old format b) a standard rsyslog.conf in new format, only c) a complex rsyslog.conf (not really working) in new format [partitioned by (just) comments] Note that being an evolution, any currently existing rsyslog.conf would also be a valid new conf (via the *same* parser). I have not thought out the full semantics and thousand other things that need to be thought of -- this actually opened up a can of worms ;) However, I find the proposed format seems to be a good compromise between the need to preserve and the need to move on, and between the need for simplicity and the need for power. As such, before I invest even more time into that format, I'd like to get some feedback on what you folks think ;) Thanks, Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
