Another option could be to use imjournal.
One of its benefits are that you get early boot messages and late
shutdown messages directly from the journal.
Am Mi., 11. Sept. 2024 um 02:21 Uhr schrieb John Chivian via rsyslog
:
>
> You can solve this with two instances of rsyslog.
>
> The first instan
You can solve this with two instances of rsyslog.
The first instance does all the system local stuff writing to local log files,
and does not require the “after=networking.service”.
The second instance reads all those files delivering the content to the network
destination (with queuing as Da
On Tue, Sep 10, 2024 at 11:26:03PM +, Andy Smith via rsyslog wrote:
> It's not quite ideal however because the *local* log files are then
> missing entries from the entire time the network is down, which can
> be quite significant. For example here is the final line before
> shutdown and first
On Tue, 10 Sep 2024, Andy Smith via rsyslog wrote:
Date: Tue, 10 Sep 2024 23:26:03 +
From: Andy Smith via rsyslog
To: rsyslog@lists.adiscon.com
Cc: Andy Smith
Subject: [rsyslog] Remote logging and systemd shutdown
Hi,
I have some Debian servers that are configured to log both locally
and
Hi,
I have some Debian servers that are configured to log both locally
and remotely, basically with:
*.* @@loghost:10514
at the end of a usual Debian /etc/rsyslog.conf file.
When rebooting or shutting down ("reboot" or "shutdown -h now") I
get as far as:
[ OK ] Stopped target Network.
5 matches
Mail list logo
