Date: Sun, 18 Jan 1998 20:22:05 +1100 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Marc Slemko <marcs@znep.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2nd call for comments: New option for newsyslog Message-ID: <Pine.BSF.3.91.980118201514.29251U-100000@panda.hilink.com.au> In-Reply-To: <Pine.BSF.3.95.980117163527.1145N-100000@alive.znep.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 17 Jan 1998, Marc Slemko wrote: > You need a generic way of allowing a HUP to be sent to any process, eg. by > specifying the PID file. Sounds good. > You need a way to only gzip the log-before-the-just-rotated one, not the > just-rotated one. This is because some programs don't immediately close > logfiles on HUP, but can take a minute or two. Good point, thanks. > You need a way to tell it to name files based on date (eg. foo.19980117) > instead of number; by number sucks for incremental backups because they > are moved every day. I knew this one, and I have a /bin/sh rollover prog which names files by dayname, monthname or weeknumber; I'll turn it into C. > You need a way to have it specify hard times instead of every x hours. As Tom pointed out, perhaps that should just be done with cron. > You need the ability to add arbitrary pre and post rotation commands. I was thinking about this, too, but perhaps the rotator should just be called from the /bin/sh script which includes the pre and post rotation commands. It seems simpler that way. > I find logrotate unusable for real log rotations because of these missing > features, but find it very silly to have to write my own stuff all the > time (or use another package) to do it. Unfortunately, extra features > don't fit too well with the config file format. logrotate? I haven't met logrotate. Thanks for the comments, Danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.980118201514.29251U-100000>