[mythtv-users] mythbackend.log is buffered?
Simon Hobson
linux at thehobsons.co.uk
Mon Oct 26 14:12:44 UTC 2015
Karl Newman <newmank1 at asme.org> wrote:
> So probably the solution would be to add a `killall -HUP mythbackend` (or mythlogserver?) lastaction command to the logrotate config.
That sounds a bit drastic, but somehow you have to get the program to start writing to a different log file. If it lacks a facility to do that while running, then you'll need to stop and restart it - but you then get into the business of working out if it's "safe" to stop it at any time.
If you don't gzip the file, then I suspect you'll find it'll keep writing to the old one until there's an event that makes it update the logging destination.
More information about the mythtv-users
mailing list