Re: The new normal of logging
- Date: Thu, 26 Oct 2017 15:25:29 -0400
- From: Roberto C. Sánchez <roberto@xxxxxxxxxx>
- Subject: Re: The new normal of logging
On Thu, Oct 26, 2017 at 07:46:12PM +0100, Jonathan de Boyne Pollard wrote:
> Roberto C. Sánchez:
> > Is this the new normal, for things to get captured in some systemd log
> > [...]?
> * https://unix.stackexchange.com/a/294206/5132 Yes.
That is very informative. In particular:
| If it can connect (as a client) to an AF_LOCAL datagram socket at
| /run/systemd/journal/syslog it writes journal data there, if forwarding
| to syslog is configured.
I need to make sure that I have that forwarding propery configured on my
| systemd itself arranges for the standard outputs and errors of (some)
| services to be attached to the /run/systemd/journal/stdout socket. So
| dæmons that log to standard error in the normal fashion have their
| output sent to the journal.
That does seem quite useful and from what I have experienced the last
few days nicely handles the case where something that should log to
syslog calls a command and then ignores its stdout/stderr. The systemd
journal was seeing that stderr text where syslog was not.
Roberto C. Sánchez