Date: Mon, 29 Oct 2001 14:14:09 -0600 From: Alfred Perlstein <bright@mu.org> To: Michael Sinz <msinz@wgate.com> Cc: obrien@FreeBSD.ORG, Mike Barcroft <mike@FreeBSD.ORG>, void <float@firedrake.org>, Kris Kennaway <kris@obsecurity.org>, hackers@FreeBSD.ORG Subject: Re: syslogd and kqueue Message-ID: <20011029141409.B15052@elvis.mu.org> In-Reply-To: <0ac642ae01eaa107d1@[192.168.1.4]>; from msinz@wgate.com on Mon, Oct 29, 2001 at 03:06:11PM -0500 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]> <0ac642ae01eaa107d1@[192.168.1.4]>
next in thread | previous in thread | raw e-mail | index | archive | help
* Michael Sinz <msinz@wgate.com> [011029 14:07] wrote:
>
> 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'm jumping in having only paid cursory attention to the current
thread so my apologies if this makes little sense.
Why not add a flag or something to syslog or newsyslog which somehow
evaluates the space available and/or creates the new files. We
could switch the system defaults via src/etc/defaults to advise
the use of this flag in 4.x and actually default to it in 5.x.
I guess this would have to address the permissions problem, perhaps
there's some way of addiding additional fields to syslog.conf?
--
-Alfred Perlstein [alfred@freebsd.org]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
http://www.morons.org/rants/gpl-harmful.php3
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?20011029141409.B15052>