[mythtv-users] What does restarting mythbackend actually do?

Jerome Yuzyk jerome at supernet.ab.ca
Tue Jan 28 22:52:45 UTC 2020


On Thursday, January 23, 2020 10:10:49 PM MST Stephen Worthington wrote:
> >I never had to do these proactive restarts before - I used to live with the
> >problem happening every few weeks. But then I started recording a
> >half-dozen hours of CNN and I started getting failed recordings every
> >other day so I started my daily routine. CNN and CTV seem to do bad
> >things. I've chalked it up to using a Shaw-provided DCS-3200MP2 and
> >Firewire (which in most places is disabled) and an old MythTV.
> >
> >But when I do get up to the latest version (31 I think, before NHL Playoffs
> >start) and I still have the same problems, I will ask more. :)
> 
> In the mean time, it should be possible to automatically schedule
> daily restarts for when MythTV is not recording.  I have a Python
> program:
> 
> http://www.jsw.gen.nz/mythtv/gaps
> 
> that tells you when a gap in the recordings of a specified size can be
> found.  So what you could do is set up a script to be run at say 04:00
> daily, then get that script to wait until the time gaps says the next
> gap will occur, and then tell systemd to reboot say 2 minutes after
> the start of that gap (to allow for any residual mythbackend activity
> to stop, and to allow for soft postroll that gaps does not see).

Thanks again, I will try it out. I wrote on in Perl some time ago but never 
got around to testing it enough to put it into production. Since yours is in 
production already, it's on my ToDo for my box.

-- 
A little of Jerome's MythTV World: http://mythtv.bss.ab.ca




More information about the mythtv-users mailing list