[EMAIL PROTECTED] wrote: > Date: Tue, 10 Jan 2006 05:46:17 -0500 (EST) > From: "Chris Pinkham" <[EMAIL PROTECTED]> > > > > I've just noticed that, when rebooting the master backend machine, > > > mysql gets shut down before the backend (because, of course, "mysql" > > > sorts before "mythbackend" and typically they're both started/stopped > > > w/the same two-digit priority in the rc scripts). This causes the > > > backend (if it's logging verbosely, which mine is) to emit a bunch of > > > This is a distribution issue, the distributor is the one who specified > > the startup/shutdown sequence, it's not in the Myth source code. > >Oh, sorry, I didn't mean to imply that this was in Myth's code. >I just wanted to figure out whether Myth did any sort of DB-related >cleanup on termination, and thus whether to ensure that the DB was, >in fact, available to it before the backend got signalled. If it >doesn't catch the signal (or doesn't do any DB-related cleanup if >it -does- catch the signal), than it doesn't matter. Otherwise, >I'll rearrange my script ordering slightly (and such a dependency >should get documented somewhere). > > Common sense says that all applications accessing the DB should be shut down cleanly before shutting down the database.
Kevin Kevin _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
