rsyslog (8.2210.0-3ubuntu2) lunar; urgency=medium

  The apparmor profile of rsyslog now defaults to be enforced on a fresh
  install and upgrades from an earlier version. Upgrades from this version
  forward won't change the enforcement status.

  Packages that add an rsyslog configuration that might be blocked by the
  apparmor profile, can add an apparmor configuration snippet in

  /etc/apparmor.d/rsyslog.d/

  This file should preferably be named like <pkg>.apparmor, but only standard
  backup extensions are excluded. See
  https://sources.debian.org/src/apparmor/3.0.8-2/libraries/libapparmor/src/private.c/#L68
  for a list.

  When the rsyslog service is started, its systemd unit file first executes
  the /usr/lib/rsyslog/reload-apparmor-profile script via ExecStartPre. That
  script will reload the rsyslogd apparmor profile including the configuration
  snippets in /etc/apparmor.d/rsyslogd.d/, if any.

  The confinement status is not changed.

  After this, the unit proceeds to start rsyslog as usual.

  For more information, check the README.apparmor file in the documentation
  directory of this package.

 -- Andreas Hasenack <andreas@canonical.com>  Sun, 05 Feb 2023 15:42:31 -0300

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 <biebl@debian.org>  Mon, 30 May 2011 18:26:51 +0200
