Comment 2 for bug 484336
Revision history for this message
| George Klein (gk-t-t-l-deactivatedaccount) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Just found this and it's covering similar ground to bug #407862. From my experience in that bug:
I agree that $DirOwner and $DirGroup should be configured.
I agree that $DirGroup, $FileGroup and $PrivDropToGroup have to be the same for rsyslog to create dynamic files properly.
However I don't believe $PrivDropToGroup _should_ have to be the same as the others.
I'm also uncomfortable running rsyslog as adm as this gives access to facilities which are irrelevant and, conversely, I don't like the idea of putting a user in group adm (so they can see logs amongst other things) into group syslog although that's waht I am doing at the moment.