* Michael Sinz <[EMAIL PROTECTED]> [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 [[EMAIL PROTECTED]]
'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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
