I would have to disagree with the compress, unless you don't mind losing log
information. It'll compress and unlink the file, and just like a move to a different
filesystem, rsync will keep writing to the log until it closes, at which point,
whatever was
written after the compress is gone.
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Colorado TC
1880 Industrial Circle
Suite D
Longmont, CO 80501
"There are some who call me.... Tim?"
[EMAIL PROTECTED]@[EMAIL PROTECTED] on 06/13/2001 03:41:12 PM
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]@SMTP
[EMAIL PROTECTED]@SMTP
[EMAIL PROTECTED]@SMTP
cc:
Subject: Re: rsyncd log file option and logrotate
Classification:
On Wed, Jun 13, 2001 at 03:54:31PM -0500, Dave Dykstra wrote:
> On Wed, Jun 13, 2001 at 04:38:52PM -0400, Scott Russell wrote:
> > David -
> >
> > No, no problem, yet. Just trying to avoid problems. :) I think the question
> > really boils down to what happens if the logfile rsyncd is writing to gets
> > moved out from under it?
>
> If it is during an open connection, it will keep the old file open from
> wherever it is moved to and write out there. That's assuming it's the
> same filesystem;
This is good news. Based on this a logrotate script like should work:
/var/log/rsyncd.log {
rotate 6
monthly
compress
missingok
}
--
Regards,
Scott Russell ([EMAIL PROTECTED])
Linux Technology Center, System Admin, RHCE.
T/L 441-9289 / External 919-543-9289
http://bzimage.raleigh.ibm.com/webcam
