| 1 |
On Friday, 15 January 2021 08:47:18 GMT n952162 wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> can anyone explain this? |
| 5 |
> |
| 6 |
> I noticed today (15. January) that the /var/log/{messages,kern.log,etc.} |
| 7 |
> files on a box were last touched on 22. November. |
| 8 |
> |
| 9 |
> sysklogd was in the rc-open /started/ state and was running. |
| 10 |
> |
| 11 |
> The configuration file, /etc/syslog.conf matches completely that file on |
| 12 |
> another machine of mine, where the logs are properly updated. |
| 13 |
> |
| 14 |
> /etc/syslog.d/ was empty on both machines. |
| 15 |
> |
| 16 |
> I sent the process a HUP signal, as follows |
| 17 |
> |
| 18 |
> sudo kill -HUP $(cat /var/run/syslogd.pid ) |
| 19 |
> |
| 20 |
> and all the log files were immediately updated and reporting. |
| 21 |
> |
| 22 |
> I rebooted my machine, and the log files are untouched, it is again |
| 23 |
> hibernating. |
| 24 |
|
| 25 |
Do you get something like this on your system? |
| 26 |
|
| 27 |
$ rc-update -s -v | grep syslog |
| 28 |
syslog-ng | default |
| 29 |
|
| 30 |
and, |
| 31 |
|
| 32 |
$ rc-service -v syslog-ng status |
| 33 |
* Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh /etc/init.d/ |
| 34 |
syslog-ng status |
| 35 |
* status: started |
Archives