[mythtv] RE: [mythtv-commits] mythtv commit: r7389 by danielk

[Buzz]

What about having an entry/setting in the database that causes mythbackend
to go into a suspended/holding/no-go state untill the setting is removed
from the database.   

Of course, the first thing that mythtv-setup should do when run  is put that
flag in, and remove it when it's done?   

When the backend detects the entry/setting has been removed from the
database, it could disconnect itself from the database, and re-start itself.


This is kinda like many daemons do  -  a re-read of config files on a HUP
signal - except it's using a database setting for the signal and the
configuration.

Seem like a good idea?   

Obviously, there's a possible race condition where mythtv-setup is
aborted/crashes and the backend gets permantly stuck on a holding
pattern.... but this could be resolved by a time-out in the backend,  or it
(the backend) could just remove the setting if it sees it there immediately
after it connects (this second option doesn't protect you from people
STARTING the backend while also running mythtv-setup, but is much simpler).

Buzz.


-----Original Message-----
From: mythtv-dev-bounces at mythtv.org [mailto:mythtv-dev-bounces at mythtv.org]
On Behalf Of David Maher
Sent: Wednesday, 5 October 2005 10:48 AM
To: mythtv-dev at mythtv.org
Subject: [mythtv] RE: [mythtv-commits] mythtv commit: r7389 by danielk

:)

-----Original Message-----
From: mythtv-commits-bounces at mythtv.org
[mailto:mythtv-commits-bounces at mythtv.org]On Behalf Of mythtv at cvs.mythtv.org
Sent: Wednesday, 5 October 2005 3:32 AM
To: mythtv-commits at mythtv.org
Subject: [mythtv-commits] mythtv commit: r7389 by danielk


      Author: danielk
        Date: 2005-10-04 17:31:32 +0000 (Tue, 04 Oct 2005) New Revision:
7389
   Changeset: http://cvs.mythtv.org/trac/changeset/7389

Modified:

   trunk/mythtv/docs/mythtv-HOWTO.sgml

Log:

Add warning to docs about shutting down backend before running mythtv-setup.