[Bucardo-general] log.bucardo logrotate

[Jonathan Brinkman]

What is the reason for not wanting to log to the old filehandle?

What about using copytruncate in logrotate? 

I'm just wondering whether the load imposed on the server by stopping /
starting can be avoided.

I too am no logrotate guru!

Many thanks

JB



-----Original Message-----
From: Greg Sabino Mullane [mailto:greg at endpoint.com] 
Sent: Friday, July 29, 2011 10:29 PM
To: Jonathan Brinkman
Cc: bucardo-general at bucardo.org
Subject: Re: [Bucardo-general] log.bucardo logrotate

On Mon, Jul 25, 2011 at 02:41:30PM -0400, Jonathan Brinkman wrote:
> Greetings
> 
> In order to manage the log.bucardo file, I've created a logrotate script. 
...

> Is there a better practice for managing this log file?

Not that I know of, but you need to tell logrotate to restart 
Bucardo so it does not try to keep logging to the old 
filehandle. I think you'd need a prerotate/bucardo stop and 
postrotate/bucardo start combo, but I'm not a logrorate guru, so 
I'll refrain from trying to post the exact syntax. :)

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8