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

2023-06-06 Thread Michael Tokarev

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



Bug#1014243: marked as done (busybox-syslogd: The 'syslog' daemon is running, but no configuration file can be found.)

2023-06-06 Thread Debian Bug Tracking System
Your message dated Tue, 6 Jun 2023 17:31:41 +0300
with message-id <9d994014-4330-109f-5040-30c21fc16...@tls.msk.ru>
and subject line Re: Bug#1014243: busybox-syslogd: The 'syslog' daemon is 
running, but no configuration file can be found.
has caused the Debian Bug report #1014243,
regarding busybox-syslogd: The 'syslog' daemon is running, but no configuration 
file can be found.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1014243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox-syslogd
Version: 1:1.35.0-1
Severity: important
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

What led up to the situation? No idea, I've never touched the configuration
(that I know of)

What exactly did you do (or not do) that was effective (or ineffective)? not
sure, it was in a cron daily report.And wasn't in the previous one.

What was the outcome of this action? received email from Cron Daily with
subject line :"[rkhunter] DebianTim - Daily report" and in the body of the
email it states: "Warning: The 'syslog' daemon is running, but no configuration
file can be found."
I have no idea where that might be to check it, the man pages point to this
program for syslog.

What outcome did you expect instead? Not to get this type of email



-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-2-rt-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages busybox-syslogd depends on:
ii  busybox  1:1.35.0-1
ii  init-system-helpers  1.63
ii  lsb-base 11.2

busybox-syslogd recommends no packages.

busybox-syslogd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

On Sat, 02 Jul 2022 12:30:48 -0500 Tim McConnell  
wrote:

Package: busybox-syslogd
Version: 1:1.35.0-1
Severity: important
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

What led up to the situation? No idea, I've never touched the configuration
(that I know of)


This is definitely not a bug in busybox-syslogd: current version of
syslogd implementation in busybox, as shipped in debian, does not
use a configuration file.

I've no idea which software produced the warning mentioned in the
subject line. Again, it is not busybox.

Closing this bugreport.

Thanks,

/mjt--- End Message ---