Re: journal stopping after sending logs on reboot

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Fr, 21.12.18 12:44, Brad Zynda (bradley.v.zynda@xxxxxxxx) wrote:

> Hi Lennart,
>
> So it looks like Jounald.conf Storage=none does not work as it says:
>
> "none" turns off all storage, all log data received will be dropped.
> Forwarding to other targets, such as the console, the kernel log buffer,
> or a syslog socket will still work however. <- does not forward to
> syslog socket

Well, it will work from journald's PoV, but whether you configure
rsyslog or whatever else to take the data is up to you.

> Changed it back to auto and it is logging but is now creating local logs
> through journal stdout again :/

Hmm?

Do you want to do turn off stdout/stderr logging for a service? Then
set StandardOutput=null and StandardError=null for that service. Or
what are you trying to do?

Lennart

--
Lennart Poettering, Red Hat
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel