[mythtv-users] I hate when this happens

[Jarod C. Wilson]

On Tuesday, Sep 16, 2003, at 18:24 US/Pacific, Bruce Markey wrote:

>> The secondary issue was suggested because a number of us have had this
>> happen not when the system goes down, but when we restart the backend
>> program.  As a solution for this, it was suggested that the recording
>> process be spawned separately, such that a backend restart wouldn't
>> affect any in-progress recordings.
>
> Then the backend really hasn't shutdown and I haven't fixed
> the problem that I needed to fix when shutting down the backend
> (lost audio buffers, VIDIOCSYNC, whatever). When the master
> restarts it kicks off any recordings that should be in progress.
> How would it find all the orphaned processes on the master and
> slaves that might be writing the same file and how would it grab
> the device files that were already busy? If I deliberatly restart
> the backend I'd want a fresh start for the recordings without
> overwriting the previous portion. If the recordings where going
> along nicely and I wanted an unblemished file I wouldn't restart
> while it was recording.

Well, there are a number of daemon processes that have both a restart 
and a reload function that behave slightly differently. Perhaps 
something along those lines would work. You could have restart kill off 
all the processes, and reload only kill off the main process, leaving 
in-progress recordings running. Have your cake and eat it too, both 
sides get what they're after. Just an idea...

--Jarod

-- 
Jarod C. Wilson, RHCE

Got a question? Read this first...
http://catb.org/~esr/faqs/smart-questions.html

MythTV, Red Hat Linux 9 & ATrpms documentation:
http://pvrhw.goldfish.org/tiki-page.php?pageName=rh9pvr250