Thank you, This is the way I will go too.
Don't you have problems changing file descriptor when process is running
? (deleted file keeping growing a filling disk space until you restart
the process)
I suggest adding "copytruncate" in logrotate configuration.


Le 30/05/2014 11:31, Tomas Barton a écrit :
> I've already refactored the logging, I'm redirecting stdout and stderr
> to a master.log or slave.log
> 
> https://github.com/deric/mesos-deb-packaging/blob/master/mesos-init-wrapper#L109
> 
> the logrotate itself it quite simple
> 
> 
> /var/log/mesos/*.log {
> daily
> missingok
> rotate 30
> compress
> delaycompress
> notifempty
> }
> 
> 
> 
> On 30 May 2014 11:14, Damien Hardy <[email protected]
> <mailto:[email protected]>> wrote:
> 
>     Hello,
> 
>     Yes I do.
>     I thought this was re right thing to do for logs.
>     But never ending file is not safe usable. This option --log_dir need
>     some rework I suppose.
>     I will go with stdout/stderr pipeline instead (using logrotate
>     copytruncate to handle open file descriptors)
> 
>     Thank you
> 
>     Le 15/05/2014 22:02, Tomas Barton a écrit :
>     > Hi Damien,
>     >
>     > do you use the `--log_dir` switch? If so, mesos is creating quite many
>     > files in a strange format:
>     >
>     > mesos-slave.{hostname}.invalid-user.log.INFO.20140409-155625.7545
>     >
>     > when you forward stdout of the service to a single file and afterwards
>     > apply simple logroate
>     > rules, you might get nicer logs.
>     >
>     > Tomas
> 
>     --
>     Damien HARDY
> 
> 

-- 
Damien HARDY
IT Infrastructure Architect
Viadeo - 30 rue de la Victoire - 75009 Paris - France
PGP : 45D7F89A

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to