From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] syslogd hibernating
Date: Fri, 15 Jan 2021 09:24:34 +0000 [thread overview]
Message-ID: <11686130.O9o76ZdvQC@dell_xps> (raw)
In-Reply-To: <50257f88-0176-db69-245b-d8a3a297ab15@web.de>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-15 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 8:47 [gentoo-user] syslogd hibernating n952162
2021-01-15 9:24 ` Michael [this message]
2021-01-15 15:08 ` n952162
2021-01-15 15:23 ` Peter Humphrey
2021-01-15 15:30 ` Michael
2021-01-15 15:39 ` Peter Humphrey
2021-01-15 16:29 ` n952162
2021-01-15 16:36 ` [gentoo-user] syslogd hibernating [RESOLVED] n952162
2021-01-15 16:50 ` [gentoo-user] syslogd hibernating n952162
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11686130.O9o76ZdvQC@dell_xps \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox