I haven't encountered any issues with that yet. It seems like a good idea, thanks.
The default values with logrotate might not suit everyone, it's just an example. It's listed as a config file, so dpkg won't replace the /etc/logrotate.d/mesos without warning. Right, could we fix the UI logs somehow? Where does the UI look for the logs? On 30 May 2014 13:30, Damien Hardy <[email protected]> wrote: > Hello, > Your point is right. > however --log_dir option provide a way to display logs for uses in HTTP > UI. That is not permit by tailing stdout/stderr. > > Best regards, > > Le 15/05/2014 17:42, Dick Davies a écrit : > > I'd try a newer version before you file bugs - but to be honest log > rotation > > is logrotates job, it's really not very hard to setup. > > > > In our stack we run under upstart, so things make it into syslog and we > > don't have to worry about rotation - scales better too as it's easier to > > centralize. > > > > On 14 May 2014 09:46, Damien Hardy <[email protected]> wrote: > >> Hello, > >> > >> Log in mesos are problematic for me so far. > >> We are used to use log4j facility in java world that permit a lot of > things. > >> > >> Mainly I would like log rotation (ideally with logrotate tool to be > >> homogeneous with other things) without restarting processes because in > >> my experience it looses history ( mesos 0.16.0 so far ) > >> > >> Best regards, > >> > >> -- > >> Damien HARDY > > -- > Damien HARDY > >
