From owner-cvs-src@FreeBSD.ORG Tue Mar 7 20:03:02 2006 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 308B716A428; Tue, 7 Mar 2006 20:03:02 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id B66C443D46; Tue, 7 Mar 2006 20:03:01 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id k27K30IJ028639; Tue, 7 Mar 2006 15:03:00 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <20060307193626.GD62485@garage.freebsd.pl> References: <200603061036.k26AaXgt047115@repoman.freebsd.org> <200603061208.11685.jhb@freebsd.org> <20060307081419.GE56506@garage.freebsd.pl> <20060307193626.GD62485@garage.freebsd.pl> Date: Tue, 7 Mar 2006 15:02:54 -0500 To: Pawel Jakub Dawidek From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.3 Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, John Baldwin Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.8 syslogd.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Mar 2006 20:03:02 -0000 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). Either that, or you will be increasing the size of syslogd by adding to it all the code which is in newsyslog, and then *also* running newsyslog for the log files which are not created by syslog. Which, of course, would be rather ironic ("Use a program called newsyslog to rotate the files which are *NOT* created by syslog"!). Why do you avoid newsyslog right now? Because it is "too big"? If so, then why would you want to pull all of newsyslog into syslogd? If not, let me know what features newsyslog is missing, and maybe we could improve newsyslog for all users, instead of modifying syslogd just to help your special case. 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. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA