On Wed, Jul 26, 2017 at 10:38 AM, Tom Horsley <horsley1953(a)gmail.com> wrote:
I once had it all figured out, reducing journald to just a proxy that
forwarded everything to syslog and kept no storage of its own.
Now I see the new version of rsyslog in fedora26 comes with a new and
improved config file syntax that is totally opaque.
Before I spend the next week trying to learn how the devil to
configure rsyslog these days, I thought I'd ask:
Has anyone on fedora 26 figured out how to get journald to just
forward everything to rsyslog which then writes the kind of plain text
files God intended? (And leaves no binary journal files anywhere on my
system).
[Can't you use the old syntax?! It hasn't been obsoleted yes; but I
guess that that day will come.]
I've just tried
- install "rsyslog"
- enable "rsyslog.service"
- set "Storage=none" and "ForwardToSyslog=yes" in
"/etc/systemd/journald.conf"
and it worked.
In the past, I remember setting
module(load="imuxsock" SysSock.Name="/run/systemd/journal/syslog")
[equivalent to "$ModLoad imuxsock" and "$SystemLogSocketName
/run/systemd/journal/syslog"]
in "/etc/rsyslog.conf" but it no longer seems to be necessary; I have
a vague memory that the socket was needed because, in the past,
'module(load="imjournal")' needed "Storage=volatile" in
"/etc/systemd/journald.conf" in order to operate.