[mythtv] Scheduler issues

ben levitt benjie at gmail.com
Wed Nov 16 23:40:41 EST 2005


Although, to be fair, it would make sense for the frontend to trigger
a reschedule when you change the "Reschedule Higher Priorities"
setting...

(The only thing better than Reading TFM is not having to...)

Ben


On 11/16/05, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> Michael T. Dean wrote:
>
> > Stuart Morgan wrote:
> >
> >> On Wednesday 16 Nov 2005 22:54, Kevin Kuphal wrote:
> >>
> >>> I don't know if it needs it, but did you restart the backend after the
> >>> change?
> >>
> >> No ... erm ... *mumbles something about a stupid scheduler setting
> >> needing a backend restart*
> >> *hangs head in shame and wonders off to find a beer*
> >
> > Well, if you don't like the fact that it requires a restart, you'll be
> > happy to know that it doesn't require a restart...
> >
> > You only have to force a reschedule.  You can do that by:
> >
> >    a) restarting the backend
> >    b) waiting until the next time the scheduler runs
> >    c) changing your schedule (i.e. add or remove a recording rule)
> >    d) running "mythbackend --resched" (which can be run while the
> > existing backend process is running)
>
>     d.5) running mythfilldatabase
>
> >    e) other ways that I haven't yet figured out...
> >
> > So, basically, the devs did a great job of making the software work
> > the way you want (so it doesn't require a restart).  Unfortunately,
> > they can't make you read the docs to find out how it works.  ;)
>
> I knew I was forgetting something...  :)
>
> Mike
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>


More information about the mythtv-dev mailing list