Date: Sat, 27 Oct 2001 00:26:22 -0400 From: Mike Barcroft <mike@FreeBSD.ORG> To: void <float@firedrake.org> Cc: Kris Kennaway <kris@obsecurity.org>, hackers@FreeBSD.ORG Subject: Re: syslogd and kqueue Message-ID: <20011027002622.C2586@coffee.q9media.com> In-Reply-To: <20011027001704.B2586@coffee.q9media.com>; from mike@FreeBSD.ORG on Sat, Oct 27, 2001 at 12:17:04AM -0400 References: <20011026233957.A9925@parhelion.firedrake.org> <20011026200436.A61058@xor.obsecurity.org> <20011027043342.A18231@parhelion.firedrake.org> <20011027001704.B2586@coffee.q9media.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Barcroft <mike@FreeBSD.ORG> writes: > void <float@firedrake.org> writes: > > On Fri, Oct 26, 2001 at 08:04:36PM -0700, Kris Kennaway wrote: > > > I assume you mean "as soon as the configuration file is modified"? > > > That would be a big violation of POLA. > > > > No ... > > Yes! 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. Just like one wouldn't expect it to create a new log file. Best regards, Mike Barcroft 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?20011027002622.C2586>