mhh... general question: would anybody object if I would not permit spaces inside file names? (one could introduce them by using dynafiles with a clever template if absolutely needed...).
Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Rainer Gerhards > Sent: Friday, January 15, 2010 5:27 PM > To: rsyslog-users > Subject: Re: [rsyslog] comments in file actions > > bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=170 > > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Rainer Gerhards > > Sent: Friday, January 15, 2010 5:23 PM > > To: rsyslog-users > > Subject: [rsyslog] comments in file actions > > > > -----Original Message----- > > > If that is modified as follows: > > > *.* /var/log/syslog # Comment goes > > > here > > > > > > > It's even worse: data is written to the > > file "/var/log/syslog # Comment goes here"! > > > > Looks like I need to find a solution at least for omfile. Thanks for > > bringing > > this issue up in this context ;) > > > > Rainer > > > > > > > then (1) no message goes to stdout; (2) nothing gets logged to > > > /var/log/syslog, because the action line specifying that action is > > > faulty. The service starts; but given that the defective action > line > > is > > > the only one in the config, it might as well have failed to start, > > > because no log output will ever be produced. In particular, > messages > > > for > > > the syslog facility will not be sent anywhere. > > > > > > I call that "silent"; as far as I can see, there is absolutely no > > > message anywhere indicating that the service had any problems with > > the > > > config. > > > > > > # rsyslogd -v > > > rsyslogd 4.5.6, compiled with: > > > FEATURE_REGEXP: Yes > > > FEATURE_LARGEFILE: Yes > > > FEATURE_NETZIP (message compression): Yes > > > GSSAPI Kerberos 5 support: No > > > FEATURE_DEBUG (debug build, slow code): No > > > Atomic operations supported: Yes > > > Runtime Instrumentation (slow code): No > > > > > > I think config parsing problems should be output unconditionally to > > > stdout; but what do I know :-) Anyway, relying on the logging > service > > > to > > > tell you about a problem with the logging service seems - umm - > > > over-confident. > > > -- > > > Jack. > > > > > > _______________________________________________ > > > rsyslog mailing list > > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > > http://www.rsyslog.com > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
