If I define a logfile with perms "-rw-r------" using the following in syslog.conf: destination d_micklog { file("/var/log/micklog" owner(mick) group(wheel) perm(0640)); }; a file is created that looks like this (ls -l output): -rw------- 1 mick wheel 57 Sep 27 10:03 /var/log/micklog Why aren't the "group" bits being set? At first I thought maybe I needed to "invert" the mode a là umode, but that isn't it. Ideas? TIA, Mick Bauer /=============================\ | Michael D.(Mick) Bauer | | Network Security Consultant | | St. Paul, Minnesota (USA) | | mick<at>visi.com | \=============================/
On Thu, Sep 27, 2001 at 10:04:07AM -0500, Michael D. (Mick) Bauer wrote:
If I define a logfile with perms "-rw-r------" using the following in syslog.conf:
destination d_micklog { file("/var/log/micklog" owner(mick) group(wheel) perm(0640)); };
a file is created that looks like this (ls -l output):
-rw------- 1 mick wheel 57 Sep 27 10:03 /var/log/micklog
Why aren't the "group" bits being set? At first I thought maybe I needed to "invert" the mode a là umode, but that isn't it. Ideas?
The permission settings from within C code are still subject to the umask of the user/process creating the file. Do you set a umask in your init scripts? Do you start syslog-ng as root with a restrictive umask setting? -- Nate
participants (2)
-
Michael D. (Mick) Bauer
-
Nate Campi