Andrew R Paterson wrote:
> On Wednesday 25 November 2015 13:57:49 Timothy Murphy wrote:
>> I'm running Fedora-23/KDE, and am trying to activate /var/log/messages,
>> but when I run "sudo systemctl restart rsyslog" I get the entry
>> imjournal: fscanf on state file `/var/lib/rsyslog/imjournal.stat
On Wednesday 25 November 2015 13:57:49 Timothy Murphy wrote:
> imjournal: fscanf on state file `/var/lib/rsyslog/imjournal.state' failed
A quick google gives something that may be relevent
https://bugzilla.redhat.com/show_bug.cgi?id=1095784
--
users mailing list
users@lists.fedoraproject.org
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
Tom Horsley 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
On Wed, 25 Nov 2015 11:59:43 +
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
install rsyslog if it isn't there
I'm running Fedora-23/KDE, and am trying to activate /var/log/messages,
but when I run "sudo systemctl restart rsyslog" I get the entry
Nov 25 11:40:35 william rsyslogd-2027: imjournal:
fscanf on state file `/var/lib/rsyslog/imjournal.state' failed
[v8.10.0 try http://www.rsyslog.com