Rainer Gerhards wrote:
> Hi folks,
>
> jumping right in the middle and looking at one issue at the other ;)
>
> Please note that nothing is silently ignored. Whenever rsyslog encounters a
> problem, a message is generated. HOWEVER, almost nobody ever looks at the
> messages emitted from the syslog facility and so the error messages are
> "lost". See also:
Rainer,
Consider please this single action line from a simple config:
*.* /var/log/syslog
If that is modified as follows:
*.* /var/log/syslog # Comment goes here
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
