[mythtv-users] Guide updates for CBS and TNT this evening

[Mike Perkins]

On 18/11/15 15:16, Michael T. Dean wrote:
> On 11/18/2015 09:24 AM, Mike Perkins wrote:
>> As an aside to this, I sometimes hit the reverse problem. I'm in the UK, and my window is set
>> 14:00 to 17:00. I have no cron job set. This slot is during the afternoon and when I often have
>> time to do maintenance.
>>
>> So I have taken the master backend down to do some reconfiguring, say a re-scan of the DVB
>> multiplexes, and when I restart the backend in order to run mythfilldatabase I discover that the
>> backend also schedules a MFDB run, even though one is already going.
>>
>> Is there any logic which tests to see if MFDB is already running, before the backend starts one off?
>
> Only in the housekeeper (and only a check to see if a mythfilldatabase that was started by the
> housekeeper is still running).  If mythfilldatabase is run by anything else, it's up to that
> something else to figure out if it should actually run it.
>
> Note, too, that there's no need for the (master or any other) backend to be running to run
> mythfilldatabase.  So, if you're going to manually run mythfilldatabase when mythbackend isn't
> running, let mythfilldatabase finish running before starting mythbackend to prevent a second
> instance of it running at the same time (but note that the housekeeper will still re-run it on its
> schedule, regardless of the successful run and the fact that we've stored the last run time).
>
I understand what you're saying, and I'll probably do that in future.

What happens now is that the manual run finishes and it nags me because the backend isn't running so 
that it can trigger the scheduler. That's why I used to start the backend before running MFDB.

-- 

Mike Perkins