Timothy Murphy wrote:
>> Has anyone managed to get information in /var/log/messages
>> as in pre-systemd days?
> From my notes on restoring sanity in fedora 22:
> edit /etc/systemd/journald.conf set Storage=none, ForwardToSyslog=yes
Thanks very much for your response,
I've made the two changes you suggest above,
and will see if they have the desired effect on re-booting.
Unfortunately, I still get the error I mentioned,
imjournal: fscanf on state file `/var/lib/rsyslog/imjournal.state' failed
> Create the file /etc/rsyslog.d/sd-socket.conf with this line in
> $AddUnixListenSocket /run/systemd/journal/syslog
> uncomment these lines in /etc/rsyslog.conf
> $ModLoad imuxsock
> $SystemLogSocketName /run/systemd/journal/syslog
I may try these, though I don't see why they should solve the problem.
I note that the file in question is empty:
sudo ls -ls /var/lib/rsyslog/imjournal.state
0 -rw-------. 1 root root 0 Oct 7 10:45 /var/lib/rsyslog/imjournal.state
I think I will have to revert to journalctl, which bad as it is
seems to be the only way of getting information on my system.
It appears to me that the systemd developers are seriously deficient
in common sense.
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin