[mythtv-users] --noautoexpire, --nosched, --nohousekeeper OK for slave backend?
cpinkham at bc2va.org
Tue Apr 17 11:21:49 UTC 2007
* On Mon Apr 16, 2007 at 10:52:52AM -0700, Yeechang Lee wrote:
> Is there any reason to not run a slave mythbackend with
> --noautoexpire, --nosched, and/or --nohousekeeper, on the assumption
> that the primary backend will take care of these functions?
Slave backends already do this internally, they don't run the
Scheduler, Housekeeper, or AutoExpire code. Older versions of Myth
used to run the AutoExpirer on all backends, but current SVN only runs
it on the master. With previous/released versions, backends would only
expire their own recordings, but in SVN the master is in charge of all
expiration and sends commands to slaves when it needs to delete a
recording on a slave. This was part of the Storage Groups modifications,
because with Storage Groups the master is in charge of storage, so it
needs to be in charge of expiration as well.
More information about the mythtv-users