Date: Sun, 28 Oct 2001 21:59:37 -0500 From: Mike Barcroft <mike@FreeBSD.ORG> To: "David O'Brien" <obrien@FreeBSD.ORG> Cc: void <float@firedrake.org>, Kris Kennaway <kris@obsecurity.org>, hackers@FreeBSD.ORG Subject: Re: syslogd and kqueue Message-ID: <20011028215937.G3418@coffee.q9media.com> In-Reply-To: <20011028180643.B59388@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Sun, Oct 28, 2001 at 06:06:43PM -0800 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> <20011028180643.B59388@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien <obrien@FreeBSD.ORG> writes: > 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. syslog.conf would require fields for user:group and permissions in order for that to work, otherwise syslogd would have no idea how you want your log files created. 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?20011028215937.G3418>