[Bug 918947] Re: rsyslog $WorkDirectory should be explicitly set
Emmanuel Fusté
918947 at bugs.launchpad.net
Tue Feb 26 16:10:47 UTC 2013
Hello,
Default $WorkDirectory /var/spool/rsyslog sould be chown to syslog:syslog in postinst.
As rsyslog drop privileges on startup by default on Ubuntu, the root:root default for /var/spool/rsyslog is useless.
Take me a lots of hours to figure it because rsyslog does not error out
or warn in such cases.
Thank you.
--
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:
Fix Released
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