Mailinglist Archive: opensuse (1239 mails)

< Previous Next >
Re: [opensuse] systemd hides important information for diagnosis of rsyslog.
В Thu, 13 Jun 2013 18:46:51 -0400
Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx> пишет:

El 13/06/13 17:56, Carlos E. R. escribió:

Why is not systemd logging this output?

Because:

1. that output is sent to stderr.

2. The unit file has StandardOutput=null as expected, otherwise a
feedback loop will ocurr (the messages emitted by rsyslog service
messages will be logged to the journal, which in turn will be forwarded
to the syslog socket, that will cause a request for a syslog
implementation to be activated..goto beggining :-) )


So you think it is better to completely remove any possibility to
find out why rsyslogd failed to start instead of rate-limiting number of
failed attempts?

Does not systemd already disables socket activation if service
failed to start several times in a sequence? Which would give user all
information needed to fix the problem and re-enable it?

3. By default StandardError= inherits StandardOutput, if you change
StandardError= goto 2 ;)



--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups