On Mon, Jun 3, 2013 at 3:52 PM, Tomas Heinrich <[email protected]> wrote:
> This is a slightly questionable change. > Typical behavior of any module is that if it is loaded but doesn't > actually do anything, a warning message is emitted to prevent mistakes in > configuration. I think I have a use case for the imuxsock module to be > loaded but inactive. > > A generalized rationale goes like this: there might be additional conf > files in /etc/rsyslog.d that just tune some parameters. If the module is > enabled, they are desirable, but when it is disabled, they can be ignored. > > The real scenario is this: systemd provides a separate conf file that > specifies where to look for the log socket. If the imuxsock module is to be > disabled, it can be done through the '$OmitLocalLogging' directive. At that > point the module is needed to parse the conf file but it does not do any > real work. > > Given an explicit directive is needed, it can be assumed that this state > is intended and no warning is necessary. > > sounds reasonable, but I would appreciate if also some other list members could comment. In any case, I'll probably merge not into 7.4 but 7.5 (the next devel version). Rainer > _______________________________________________ > 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.
