[mythtv-commits] Re: Ticket #617: Allow non-blocking client connections

MythTV mythtv at cvs.mythtv.org
Thu Nov 10 15:11:52 EST 2005


#617: Allow non-blocking client connections
-----------------------------+----------------------------------------------
 Reporter:  gnassas at mac.com  |        Owner:  gnassas at mac.com
     Type:  patch            |       Status:  closed         
 Priority:  minor            |    Milestone:  0.19           
Component:  mythtv           |      Version:  head           
 Severity:  medium           |   Resolution:  wontfix        
-----------------------------+----------------------------------------------
Comment (by paulh):

 This patch doesn't look like it will work as intended to me anyway.
 What happens in the case where the combined FE/BE is started to
 record something. You still need mythwelcome to connect to the
 BE as a blocking client even if for only a few seconds so as to trigger
 the BE  into shutting down when idle. Otherwise it will spin waiting for a
 client to connect because of the 'block shutdown before client connected'
 setting.

 This is how it works now when starting up to record something.
 The following assumes you have the 'block shutdown before client
 connected' set to yes.

 - the BE starts up , starts any pending recordings and spins waiting for a
 client to
   connect. It will wait in this condition forever until at least one
 client has connected
   even after all recordings have finished.

 - mythwelcome starts up as a normal client (blocks shutdown from
 happening)

 - the BE notices a client has connected and releases it blockshutdown
 flag.
   It is now free to shutdown when it becomes idle and there are no
 blocking clients
   connected.

 - after a short period mythwelcome sends an ALLOW_SHUTDOWN command to
   the BE which tells it to ignore mythwelcomes connections when making the
 decision of whether to
   shut down when idle or not.

 - after all recordings have finished and the BE becomes idle it shuts the
 computer down.


 If you untick the 'Automatically Start Myth Frontend' setting on the
 combined FE/BE
 machine does everything work OK apart from the fact that if you start it
 up yourself and
 then leave it to boot up unattended when you come back to it you find it
 has shutdown again
 because the frontend didn't start automatically?

 Maybe a better approach to the problem would be to make mythwelcome a
 little
 smarter as to when it sends the 'ALLOW_SHUTDOWN' command to the BE and/or
 when
 it starts up the FE automatically?

 Paul

-- 
Ticket URL: <http://cvs.mythtv.org/trac/ticket/617>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list