Package: busybox-syslogd
Version: 1:1.35.0-1
Severity: important

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

Reply via email to