Date: Mon, 6 Mar 2006 12:33:57 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Pawel Jakub Dawidek <pjd@FreeBSD.org>, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.8 syslogd.c Message-ID: <p06230917c03221d8700d@[128.113.24.47]> In-Reply-To: <200603061036.k26AaXgt047115@repoman.freebsd.org> References: <200603061036.k26AaXgt047115@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:36 AM +0000 3/6/06, Pawel Jakub Dawidek wrote: >pjd 2006-03-06 10:36:33 UTC > > FreeBSD src repository > > Modified files: > usr.sbin/syslogd syslogd.8 syslogd.c > Log: > By default (for security reasons) syslogd(8) doesn't create > log files when they don't exist, but sometimes its quite > useful (eg. we use non-standard log files and memory backed > /var/, which is populated on boot). > > Add -C option which tells syslogd(8) to create log files if > they don't exist. Hmm. Note that newsyslog includes an option to automatically create files. Presumably the log files created by syslogd would need to be rotated, in which case they'll already have entries in newsyslog.conf. The advantage of creating them in newsyslog is that newsyslog knows what owner, group, and chmod bits the files should have. I would not say that I object to the idea of having this option in syslogd, but I'd think people would be much better off using newsyslog to create any of the files. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06230917c03221d8700d>