On Mon, Dec 16, 2013 at 7:15 AM, Pavel Levshin <[email protected]> wrote:
> 16.12.2013 5:17, David Lang: > > >> OK, for me, this just is not old-syntax example. By old-style, I mean >>> this and alike: >>> >>> http://www.rsyslog.com/doc/rsyslog_conf_global.html >>> >>> Do you think that *$MainMsgQueueWorkerThreadMinumumMessages* is good >>> for something new? Why not use new syntax? For now, the reason is very sad: >>> it is very hard to find how to write it in new syntax. >>> >> >> some things like workdir are global, for those it's much clearer to use >> the old style format that is separate from everything else than the new >> style format which makes it look like it's part of a queue configuration >> when it's really a global setting. >> >> > Ok, so it will need an architect to clean up this mess. > > Sure, global configuration directives should not belong to any queue, and > if they do, it is a mistake. They could have own 'global' section. > > And, indeed, this exactly is where they live: http://www.rsyslog.com/doc/global.html Note that the link to this page was broken. I just fixed that. Again, not all global directives are supported by the new style. There is an important difference between new- and old-style global directives. In old-style, they could be re-set as often as one liked, with the end result becoming a mess (especially when include files used conflicting directives) and nobody really knowing which one was used. The new style throws errors if the same setting is changed later on. So there *is* value in using new style. But... 24hr problem... more important things to be done first, before moving over the rest of the statements. Not even sure if actuall all re-sets throw errors, but that is what it should. Rainer Rainer > Don't you think that our discussion clearly shows why a dedicated > committer is needed? :) > > > -- > Pavel Levshin > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
