From owner-freebsd-hackers Mon Oct 29 12: 6:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with SMTP id 50FD037B405 for ; Mon, 29 Oct 2001 12:06:36 -0800 (PST) To: obrien@FreeBSD.ORG Cc: Mike Barcroft , void , Kris Kennaway , hackers@FreeBSD.ORG Received: From MAIL.TVOL.NET (10.1.1.4[10.1.1.4 port:1595]) by mx.wgate.comMail essentials (server 2.429) with SMTP id: <11048@mx.wgate.com>transfer for ; Mon, 29 Oct 2001 3:04:10 PM -0400 ;transfer smtpmailfrom X-MESINK_Inbound: 0 X-MESINK_MailForType: SMTP X-MESINK_SenderType: SMTP X-MESINK_Sender: msinz@wgate.com X-MESINK_MailFor: hackers@FreeBSD.ORG Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.tvol.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)id VVFXRQFN; Mon, 29 Oct 2001 15:04:57 -0500 Received: from wgate.com (localhost [127.0.0.1])by sinz.eng.tvol.net (8.11.6/8.11.6) with ESMTP id f9TK6B532488;Mon, 29 Oct 2001 15:06:11 -0500 (EST)(envelope-from msinz@wgate.com) Date: Mon, 29 Oct 2001 15:06:11 -0500 From: Michael Sinz Organization: WorldGate Communications Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.4-RC i386) X-Accept-Language: en Subject: Re: syslogd and kqueue References: <20011026233957.A9925@parhelion.firedrake.org> <20011026200436.A61058@xor.obsecurity.org> <20011027043342.A18231@parhelion.firedrake.org> <20011027001704.B2586@coffee.q9media.com> <20011027002622.C2586@coffee.q9media.com> <06ea43fb01df2807d1@[192.168.1.4]> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit x-receiver: hackers@FreeBSD.ORG x-sender: msinz@wgate.com MIME-Version: 1.0 Message-ID: <0ac642ae01eaa107d1@[192.168.1.4]> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Sat, Oct 27, 2001 at 12:26:22AM -0400, Mike Barcroft wrote: > > Just to clarify. This is still a POLA violation. If a log file is > > pulled out from underneath syslogd(8), one wouldn't expect it to start > > logging again, even if the file was re-created. > > I disagree, if the file was re-created. > > Actually, I find it weird and counter intuitive that syslogd will not > log to the files in the config file (/etc/syslog.conf) unless they > already exists. It really feels like we are living with a programming > bug 25 years later.... > > If I didn't want syslogd to log something, I would not have it in > syslog.conf. This has bitten a number of support people - a server fills up and they get a bit too loose with the "rm" command and logging stops. I actually somewhat understand why syslogd does not open/create the file using the current syslog.conf syntax - it is hard to descript user/group ownership and access rights in the syslog.conf. The thing that syslogd does is write to the file that already exists such that the access rights can be controlled externally to the syslogd process. I really hate this and wish I could change this without suddenly causing all of us old-timers to surprised. For me I see two different POLA issues: 1) For those who have already understood and used syslog for a long time - syslogd does not create a file... 2) For those who have not had much time with syslog - it is rather upsetting to have configured syslog.conf and you either HUP or reboot and yet the logging does not start. As the world of FreeBSD (and other syslog systems) increases, the ratio of people is catagory #2 vs #1 will continue to increase. (Most people do not spend much time playing with syslogd) -- Michael Sinz ---- Worldgate Communications ---- msinz@wgate.com A master's secrets are only as good as the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message