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

Jamie Strandboge jamie at ubuntu.com
Fri Mar 2 15:44:42 UTC 2012


Unmilestoning. I want to wait on Debian but don't want this to block
anything on 12.04. I had hoped Debian would've responded by now, but oh
well.

** Changed in: rsyslog (Ubuntu Precise)
    Milestone: ubuntu-12.04-beta-2 => None

-- 
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:
  Triaged
Status in “rsyslog” source package in Precise:
  Triaged
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




More information about the foundations-bugs mailing list