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