| 1 |
On Friday, 15 January 2021 15:08:15 GMT n952162 wrote: |
| 2 |
> On 1/15/21 10:24 AM, Michael wrote: |
| 3 |
> > On Friday, 15 January 2021 08:47:18 GMT n952162 wrote: |
| 4 |
> >> Hello, |
| 5 |
> >> |
| 6 |
> >> can anyone explain this? |
| 7 |
> >> |
| 8 |
> >> I noticed today (15. January) that the /var/log/{messages,kern.log,etc.} |
| 9 |
> >> files on a box were last touched on 22. November. |
| 10 |
> >> |
| 11 |
> >> sysklogd was in the rc-open /started/ state and was running. |
| 12 |
> >> |
| 13 |
> >> The configuration file, /etc/syslog.conf matches completely that file on |
| 14 |
> >> another machine of mine, where the logs are properly updated. |
| 15 |
> >> |
| 16 |
> >> /etc/syslog.d/ was empty on both machines. |
| 17 |
> >> |
| 18 |
> >> I sent the process a HUP signal, as follows |
| 19 |
> >> |
| 20 |
> >> sudo kill -HUP $(cat /var/run/syslogd.pid ) |
| 21 |
> >> |
| 22 |
> >> and all the log files were immediately updated and reporting. |
| 23 |
> >> |
| 24 |
> >> I rebooted my machine, and the log files are untouched, it is again |
| 25 |
> >> hibernating. |
| 26 |
> > |
| 27 |
> > Do you get something like this on your system? |
| 28 |
> > |
| 29 |
> > $ rc-update -s -v | grep syslog |
| 30 |
> > |
| 31 |
> > syslog-ng | default |
| 32 |
> > |
| 33 |
> > and, |
| 34 |
> > |
| 35 |
> > $ rc-service -v syslog-ng status |
| 36 |
> > |
| 37 |
> > * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh |
| 38 |
> > /etc/init.d/ |
| 39 |
> > |
| 40 |
> > syslog-ng status |
| 41 |
> > |
| 42 |
> > * status: started |
| 43 |
> |
| 44 |
> $ rc-service -v syslog-ng status |
| 45 |
> * rc-service: service `syslog-ng' does not exist |
| 46 |
> |
| 47 |
> $ rc-service -v syslog status |
| 48 |
> * rc-service: service `syslog' does not exist |
| 49 |
> |
| 50 |
> $ rc-service -v syslogd status |
| 51 |
> * rc-service: service `syslogd' does not exist |
| 52 |
> |
| 53 |
> $ rc-service -v sysklogd status |
| 54 |
> * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh |
| 55 |
> /etc/init.d/sysklogd status |
| 56 |
> * status: started |
| 57 |
> |
| 58 |
> $ rc-update -s -v | grep syslog |
| 59 |
> |
| 60 |
> $ rc-update -s -v | grep sysklog |
| 61 |
> sysklogd | default sysinit |
| 62 |
> |
| 63 |
> |
| 64 |
> I ran that as a script on a machine where the logs are properly updated: |
| 65 |
> |
| 66 |
> 01~>bash -x /tmp/test |
| 67 |
> + rc-service -v syslog-ng status |
| 68 |
> * rc-service: service `syslog-ng' does not exist |
| 69 |
> + rc-service -v syslog status |
| 70 |
> * rc-service: service `syslog' does not exist |
| 71 |
> + rc-service -v syslogd status |
| 72 |
> * rc-service: service `syslogd' does not exist |
| 73 |
> + rc-service -v sysklogd status |
| 74 |
> * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh |
| 75 |
> /etc/init.d/sysklogd status |
| 76 |
> * status: started |
| 77 |
> + rc-update -s -v |
| 78 |
> + grep syslog |
| 79 |
> + rc-update -s -v |
| 80 |
> + grep sysklog |
| 81 |
> sysklogd | default |
| 82 |
|
| 83 |
Substitute your syslog program's name for syslog-ng. Michael did say |
| 84 |
"something like." |
| 85 |
|
| 86 |
-- |
| 87 |
Regards, |
| 88 |
Peter. |
Archives