On Friday, 15 January 2021 08:47:18 GMT n952162 wrote:
> Hello,
>
> can anyone explain this?
>
> I noticed today (15. January) that the /var/log/{messages,kern.log,etc.}
> files on a box were last touched on 22. November.
>
> sysklogd was in the rc-open /started/ state and was running.
>
> The configuration file, /etc/syslog.conf matches completely that file on
> another machine of mine, where the logs are properly updated.
>
> /etc/syslog.d/ was empty on both machines.
>
> I sent the process a HUP signal, as follows
>
> sudo kill -HUP $(cat /var/run/syslogd.pid )
>
> and all the log files were immediately updated and reporting.
>
> I rebooted my machine, and the log files are untouched, it is again
> hibernating.
Do you get something like this on your system?
$ rc-update -s -v | grep syslog
syslog-ng | default
and,
$ rc-service -v syslog-ng status
* Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh /etc/init.d/
syslog-ng status
* status: started
signature.asc
Description: This is a digitally signed message part.
