[Bug 484336] Re: /etc/rsyslog.conf permissions incorrect/missing for creation of dynamic files

[Simon Déziel]

I confirm that the patch in comment #1 works on Lucid. Setting the
$DirOwner and $DirGroup was essential to have rsyslog to creating new
directories that are part of the path to the dynamic files
("/var/log/central/%$YEAR%/%$MONTH%/%$DAY%/%HOSTNAME%.log").

I agree that using "$PrivDropToGroup adm" comes with a bigger risk than
using "$PrivDropToGroup syslog" but the former provides out of the box
compatibility with other tools like logcheck.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/484336

Title:
  /etc/rsyslog.conf permissions incorrect/missing for creation of
  dynamic files

Status in “rsyslog” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: rsyslog

  When using templates to create dynamic directories and files with
  rsyslog, rsyslog can create the directories, but does not have the
  appropriate permissions to create files within them.

  By default, directories created by rsyslog are owned root:root and
  generates an error in /var/log/syslog as follows:

                      rsyslogd: Cout not open dynamic file '...' -
  discarding message

  Furthermore, adding $DirOwner and $DirGroup to match those of
  $FileOwner and $FileGroup, the setting '$PrivDropToGroup syslog'
  further prevents rsyslog from creating dynamic files.  Setting
  '$PrivDropToGroup adm' resolves this issue.

  Attached is a patch that corrects these issues.

  Rich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/484336/+subscriptions