cvs commit: src/usr.sbin/syslogd syslogd.8 syslogd.c
Pawel Jakub Dawidek
pjd at FreeBSD.org
Tue Mar 7 12:13:29 PST 2006
On Tue, Mar 07, 2006 at 03:02:54PM -0500, Garance A Drosehn wrote:
+> At 8:36 PM +0100 3/7/06, Pawel Jakub Dawidek wrote:
+> >Most usefull will be to have one configuration file for syslogd
+> >and newsyslog, eg.:
+> >*.* /var/log/all.log 600 7 * @T00 J
+> >security.* /var/log/security 600 10 100 * JC
+> >And teach syslogd to create configuration files with proper
+> >owner+permission on start.
+> Sigh. Except then you have the "syslog" config file with
+> information about log files that syslog has nothing to do
+> with (such as log files written to by apache, etc). [...]
+> In any case, I'll bow out at this point saying that the
+> update to syslogd is small enough that I do not object to
+> it. All I wanted to say was that it strikes me as the
+> wrong solution. If we add an option to syslogd so it will
+> create it's own log files, then it would be reasonable to
+> add a similar option to every other program that writes
+> log files. I don't understand why we'd want to go down
+> that path.
Actually most of the programms that use their own log files create those
log files by default...
Pawel Jakub Dawidek http://www.wheel.pl
pjd at FreeBSD.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-src/attachments/20060307/5534fbb5/attachment.bin
More information about the cvs-src