[mythtv-users] Backend/Scheduler issue

[Calvin Harrigan]

Donavan Stanley wrote:

>On Thu, 27 Jan 2005 10:56:39 -0500, Calvin Harrigan
><charriglists at bellsouth.net> wrote:
>  
>
>>Greetings all,
>>    I have been using mythtv for almost 2 years,  I currently run
>>version 0.15.1.  Everything works fine for most part.  The biggest
>>annoyance that I have is with the scheduler.  My box is a combo
>>front/back end with 1 pvr-250 card.  During boot up I make use of a
>>script that determines whether the backend thinks that it was awaken by
>>the user or by a scheduled recording.  That script then creates a new
>>.xinitrc file that either starts up mythfrontend or a small splash
>>screen program that simply states that myth is in auto mode, press any
>>key to start the frontend.  I did this so that the machine will
>>automatically shutdown after the recording was finished because a
>>frontend never connected.  This all works fine and dandy.  Problem is
>>that during startup the query that determines whether the backend is in
>>user or auto mode does not take into account whether a program has been
>>previously recorded or disabled.  So if I start myth manually and a
>>recording should have been running or will be running shortly (though
>>previously recorded, you know grayed out in the "fix scheduled
>>recording" screen) it assumes that it is in automode.  Problem is that
>>the backend itself knows that there are no pending recordings and shuts
>>down in 30 seconds because the frontend was never started.  Whew, what a
>>mouthful.  Hope it was clear as to what the problem is.  Please ask any
>>questions needed to clear it up.  Has anyone had a similar problem or
>>has it been fixed in newer versions?  I've put off upgrading to 0.16
>>because of the issues I have read about on the mailing list.
>>
>>Thank you for any insight, advice.
>>    
>>
>
>
>You can alwasy grep the output from the backend when it starts, all
>the info you need about why it was started.
>  
>
It started because I manually started it.  The problem is that it thinks 
it was started automatically to record a program.  It thinks this 
because a disabled recording event should have been recording or will be 
recording soon.

Calvin...