I ran into this today. If I understand correctly the privilege drop happens before the chown though it should be the other way around, the chown should happen while root and then privileges should be dropped. And in any case the failure of chown should not prevent the logs from writing. The solution seems to be that $FileGroup and $PrivDropToGroup should match. From a security perspective setting $FileGroup to to syslog is the safest course of action.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/484336 Title: /etc/rsyslog.conf permissions incorrect/missing for creation of dynamic files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/484336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
