void wrote: > 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
never do a mv/touch on a log file to avoid full filled file systems, use cp instead... cp log log.0 (there is a delta here which can be handled w/ tail -0 -f) cp /dev/null log this has the advantage to work w/ every daemons, even the ones wich don't handle SIGHUP as well as simple redirections (daemon > log). > kill -1 `cat /var/run/syslogd.pid` > gzip log.0 Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
