Your message dated Fri, 18 Apr 2025 23:03:27 +0200
with message-id <[email protected]>
and subject line Re: rsyslog: please allow disabling of Debian standard log
files
has caused the Debian Bug report #488880,
regarding rsyslog: please allow disabling of Debian standard log files
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 [email protected]
immediately.)
--
488880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488880
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsyslog
Version: 3.16.2-1
Severity: wishlist
Hi,
this might be an upstream issue.
I'd like to completely disable Debian's default log locations. I can
do this by commenting out the configuration from /etc/rsyslog.conf,
but would have live with dpkg-conffile questions every time an update
happens.
IMO, it would be better to have the actual logging in
/etc/rsyslog.d/zz_default_debian so that one can simply delete the file.
I have solved this temporarily by a file
/etc/rsyslog.d/00_zgserver.conf:
auth.*,authpriv.* /var/log/syslog/auth.log
*.*;auth.none,authpriv.none -/var/log/syslog/syslog
*.emerg *
*.* ~
This does not, however, keep rsyslog from creating the normal files in
/var/log, and from complaining that /var/log/syslog is a directory
now. This is an acceptable workaround, but I'd love to have a more
elegant solution.
It would for example be possible to implement an option that keeps new
files from being actually created until the first message is actually
written to it, with the default being "create the file on rsyslogd
startup" for compatibility.
Greetings
Marc
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25.9-scyw00225 (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages rsyslog depends on:
ii libc6 2.7-12 GNU C Library: Shared libraries
ii lsb-base 3.2-12 Linux Standard Base 3.2 init scrip
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages rsyslog recommends:
ii logrotate 3.7.1-3 Log rotation utility
-- no debconf information
--- End Message ---
--- Begin Message ---
This is an *old* bug report, I know...
On Sat, 28 Dec 2024 07:34:25 +0100 Josip Rodin
<[email protected]> wrote:
Hi,
I noticed recently on some older machines how my /var/log/ was getting
spammed by duplicate messages, and was very happy to see that newer machines
aren't suffering from it, because of the cleanups in the global rules done
a couple of years back,
https://salsa.debian.org/debian/rsyslog/-/commits/debian/master/debian/rsyslog.conf?ref_type=heads
This helps alleviate some of the concerns from the older comments in this
bug report.
The general issue remains - should the default rsyslog config be split up
into .d/ files. The general trend has been in favor of doing this, because
it should ease customization by users. Are we worried that there are some
dependencies on the files created by the default rules?
I thought about this and concluded that splitting up /etc/rsyslog.conf
is probably not too helpful or rather, it's not clear where and why to
split it.
The good news is, that you can drop in your custom rules in
/etc/rsyslog.d/ and use "& stop" to prevent further processing by the
rules in /etc/rsyslog.conf.
Regards,
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
