Larry Ploetz wrote:
On 1/7/09 10:15 AM, Mark Post wrote:
On 1/7/2009 at 5:44 AM, John
Summerfield<deb...@herakles.homelinux.org>
wrote:
-snip-
logrotate expects you're logging sensibly. John is not.
"sensibly" means the program can close and reopen the logfile on demand.
That is not a requirement for logrotate. If nothing else the
"copytruncate" parameter will do what is desired. I had to wind up
using that for ntpd, since it never closes its log file, and any
signals ntpd gets result in it shutting down.
Right, but copytruncate doesn't create sparse files when it's rotating
old generations (i.e., it probably reads the file and creates real \x00
where there was sparse-ness):
I see no reason logrotate should not handle sparse files well when
copying them.
06:42 [sum...@numbat ~]$ cp --help | grep sparse
--sparse=WHEN control creation of sparse files
This is probably the best way of cleaning the NULs people are concerned
about.
--
Cheers
John
-- spambait
1aaaa...@coco.merseine.nu z1aaaa...@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
