rsyslog (8.2310.0-3) unstable; urgency=medium The sandboxing features enabled in 8.2310.0-1, specifically PrivateDevices=yes, broke the forwarding of messages to /dev/xconsole. It is thus recommended to move the named pipe to /run/ and make /dev/xconsole a symlink pointing at /run/xconsole. The example files /usr/share/doc/rsyslog/examples/tmpfiles.d/xconsole.conf and /usr/share/doc/rsyslog/examples/rsyslog.d/xconsole.conf haven been updated to reflect this new setup. If you have forwarding to xconsole enabled, please update your local configuration in /etc/rsyslog.d and /etc/tmpfiles.d accordingly. -- Michael Biebl Mon, 27 Nov 2023 08:01:34 +0100 rsyslog (8.2310.0-1) unstable; urgency=medium Enable various systemd sandboxing and security hardening features in rsyslog.service. The command "systemd-analyze security rsyslog.service" provides an overview of the active security and sandboxing settings. Should you run a custom setup which is broken by those changes, you can disable individual settings by creating a drop-in config file for rsyslog.service via "systemctl edit rsyslog.service". See also "man capabilities" and "man systemd.exec". -- Michael Biebl Tue, 10 Oct 2023 17:03:41 +0200 rsyslog (5.8.1-1) unstable; urgency=low The way rsyslog processes SIGHUP has changed. It no longer does a reload of its configuration, but simply closes all open files, which is a much more lightweight operation. To apply a changed configuration, rsyslogd needs to be restarted now. As a consequence, the reload action has been dropped from the init script. A new action called "rotate" was added to the init script, which signals rsyslogd to close all open files. This new action is used in the rsyslog logrotate configuration file. For more information, see: http://www.rsyslog.com/doc/v4compatibility.html http://www.rsyslog.com/doc/v5compatibility.html -- Michael Biebl Mon, 30 May 2011 18:26:51 +0200