Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

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

154 views
Skip to first unread message

W. Martin Borgert

unread,
Aug 24, 2018, 10:50:02 AM8/24/18
to
busybox-syslogd.service
busybox-klogd.service

Michael Tokarev

unread,
Jan 21, 2023, 12:00:04 PM1/21/23
to
Control: tag -1 + moreinfo

On Fri, 24 Aug 2018 16:39:00 +0200 "W. Martin Borgert" <deb...@debian.org> wrote:
> Package: busybox-syslogd
> Version: 1:1.22.0-19
> Tags: patch
>
> Please add systemd .service files to busybox-syslogd.
> The attached files are taken from OpenEmbedded and
> seem to work on my embedded device on Debian 9.
> Thanks in advance!

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.

Thanks,

/mjt

Michael Tokarev

unread,
Jun 6, 2023, 12:40:05 PM6/6/23
to
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
0 new messages