Date: Sat, 27 Oct 2001 04:33:42 +0100 From: void <float@firedrake.org> To: Kris Kennaway <kris@obsecurity.org> Cc: void <float@firedrake.org>, hackers@FreeBSD.ORG Subject: Re: syslogd and kqueue Message-ID: <20011027043342.A18231@parhelion.firedrake.org> In-Reply-To: <20011026200436.A61058@xor.obsecurity.org> References: <20011026233957.A9925@parhelion.firedrake.org> <20011026200436.A61058@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 26, 2001 at 08:04:36PM -0700, Kris Kennaway wrote: > On Fri, Oct 26, 2001 at 11:39:57PM +0100, void wrote: > > If syslogd used the kqueue interface, I believe it could open a new log > > file as soon as it was created, rather than waiting to receive a signal. > > Would this be worth doing, or would it be too big a divergence from the > > traditional behavior? > > I assume you mean "as soon as the configuration file is modified"? > That would be a big violation of POLA. No ... The traditional log-rotation dance goes something like: mv log log.0 touch log kill -1 `cat /var/run/syslogd.pid` gzip log.0 I'm suggesting that the "kill" could be left out if syslogd got the same smarts as "tail -F". -- Ben "An art scene of delight I created this to be ..." -- Sun Ra 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?20011027043342.A18231>