Date: Sun, 28 Oct 2001 18:06:43 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Mike Barcroft <mike@FreeBSD.ORG> Cc: void <float@firedrake.org>, Kris Kennaway <kris@obsecurity.org>, hackers@FreeBSD.ORG Subject: Re: syslogd and kqueue Message-ID: <20011028180643.B59388@dragon.nuxi.com> In-Reply-To: <20011027002622.C2586@coffee.q9media.com>; from mike@FreeBSD.ORG on Sat, Oct 27, 2001 at 12:26:22AM -0400 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011028180643.B59388>