syslog-ng weirdness upgrading from 4.7 to 4.8

nate freebsd at
Tue Apr 8 10:51:00 PDT 2003

I upgraded to freebsd 4.8 from 4.7 last week and portupgrade
reported it upgraded syslog-ng from syslog-ng-1.4.17 to
syslog-ng-1.6.0.r1 and libol-0.2.23 to libol-0.3.9
(libol is required by syslog-ng)

and while syslog-ng is working I cannot get it to store files
that are group readable. In the past this has been no problem,
but now syslog-ng seems to insist upon permissions of 600. I
even went sofar as to set a umask of 137, in the syslog-ng init
script, which sets permissions on newly created files to 640,
but that seems to have no effect, syslog-ng randomly(?) changes
permissions back to 600 even after I set them to 640 myself.
I have logrotate run weekly and create files that are 640:

/var/log-ng/* {
        create 0640 root wheel
        errors my at email.address
        rotate 26
        olddir /var/log-ng/archive

but syslog-ng again changes it back to 600. driving me crazy :)

I don't see anything in the syslog-ng manpage that can set file I'm at a loss! I have been running syslog-ng
on freebsd 4.7 with no problems since about september 2002.

anyone else experience this?



More information about the freebsd-questions mailing list