[Bug 918947] Re: rsyslog $WorkDirectory should be explicitly set

[Launchpad Bug Tracker]

This bug was fixed in the package rsyslog - 5.8.6-1ubuntu7

---------------
rsyslog (5.8.6-1ubuntu7) precise; urgency=low

  * debian/rsyslog.conf: set $WorkDirectory to /var/spool/rsyslog, which is
    the example location in documentation. When not configured it defaults to
    '/', which is undesirable. (LP: #918947, Closes: #656535)
  * debian/rsyslog.dirs: add /var/spool/rsyslog/
  * debian/usr.sbin.rsyslogd:
    - adjust for $WorkDirectory
    - allow 'r' on /var/log/** too (for imfile)
 -- Jamie Strandboge <jamie at ubuntu.com>   Wed, 07 Mar 2012 08:26:54 -0600

** Changed in: rsyslog (Ubuntu Precise)
       Status: In Progress => Fix Released

-- 
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/918947

Title:
  rsyslog $WorkDirectory should be explicitly set

Status in “rsyslog” package in Ubuntu:
  Fix Released
Status in “rsyslog” source package in Precise:
  Fix Released
Status in “rsyslog” package in Debian:
  New

Bug description:
  In testing the imfile functionality, I learned that when
  $WorkDirectory is not explicitly set, it defaults to '/'. This means
  that state files (and presumably other files) are written directly in
  /. This violates the FHS and is generally weird.

  Granted, it appears that at least with imfile, the file is created
  then unlinked while keeping the fd open, I am not sure of the other
  uses of WorkDirectory. At a minimum, setting WorkDirectory allows us
  to adjust the AppArmor profile to have a reliable location.

  Upstream documentation uses /var/spool/rsyslog, which seems like a
  sane default. Patch to achieve this is forthcoming.

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