Date: Tue, 10 Jul 2001 13:54:10 -0700 From: "brian j. peterson" <rbw@myplace.org> To: freebsd-questions@FreeBSD.org Subject: syslogd logfile turnover and permissions Message-ID: <20010710135410.N84474@malkavian.org>
next in thread | raw e-mail | index | archive | help
when syslogd turns over /var/log/messages (e.g. "Jun 15 13:00:00 monkey newsyslog[63011]: logfile turned over"), both the newly created /var/log/messages and the /var/log/messages.0.gz files have their per- missions set to 0755. on a system i help admin, we are using a third-party application to log some system statistics with syslogd. the local7.* selector is used in /etc/syslog.conf to direct the output from the aforementioned application into a separate file. the problem i am running into is that syslogd seems to insist on setting the permissions for that file to 0700. i can manually change it to 0750 (which is what i would like it to be), but the file is put back to 0700 when syslogd turns the file over. is there some way to control what permissions syslogd sets on the files it creates? are the permissions on new files dictated by the permissions on the existing file at the time syslogd was run? any help or suggestions would be appreciated. thanks, brian -- --===-----=======-----------=============-----------------=================== | rbw aka bjp | god's final message to his creation: | | rbw@myplace.org | we apologize for the inconvenience. | ===================-----------------=============-----------=======-----===-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010710135410.N84474>