[mythtv] Re: Ticket #430: Tuner busy on consecutive recordings

[Daniel Kristjansson]

On Sat, 2005-10-08 at 15:42 -0700, Jack Hyde wrote:
> The clock drift sounds like it's probably the cause of my woes. The clocks
> are normally synced to the same ntp server but I just discovered that the
> ntp process wasn't being launched because the service name changed after an
> update and I never added it to the default run level. The difference that
> had accumulated was 12 seconds, which might be the reason why I keep getting
> screwed. I fixed the problem, and will see what happens with the next bunch
> of recordings. 

Can you un-sync your clocks so that the slave is "slower"
by 12 seconds again, and then test this patch.

It should shutdown the recording at the earlier of the
times on the master and slave backends. It is of course
best to have the two in sync, but you shouldn't lose 
recordings entirely if they are not in sync.

-- Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: consecutive-recordings-fix-v1.patch.bz2
Type: application/x-bzip
Size: 3754 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-dev/attachments/20051009/735f5d56/consecutive-recordings-fix-v1.patch.bin