Bug#907189: busybox-syslogd: Please provide systemd .service files (attached)

[Michael Tokarev <mjt@tls.msk.ru>]

21.01.2023 19:49, Michael Tokarev wrote:
..
> What's the reason to provide these systemd services for busybox-syslogd?
>
> In my view, busybox-syslogd can be used as a minimal syslogging service
> on a bare minimal system without much else besides busybox itself.
> On a system with systemd, systemd-journald is already running, and provides
> far better logging services than busybox-syslogd, including kernel logging
> and /dev/log redirection.
>
> I don't really see the point in providing systemd .services for busybox-syslogd.

After some thinking and facing issues with logging on a low-power machine where
systemd-journald is taking just too much time to find journal entries, I think
it is a good idea to provide busybox-syslogd.

In /etc/init.d/busybox-klogd, we have if running_under_systemd; then exit; fi -
added by me, with a comment stating klogd makes no sense under systemd. This
is apparently wrong, - yes, journald does intercept kernel log and logs it to
the journal, but it suffers from the same prob: on a low-power machine these
journal entries takes ages to retrieve. So it makes sense to package klogd
too, and to provide systemd service file for it.

Doing that now.

/mjt