[mythtv-users] Conversion from single backend to new master/slave backend?

[Brian Guilfoos]

David Frascone wrote:
> Cool -- db move worked!

:D

> So -- as an intermediate test, I'm going to have my database server run 
> mythjob queue . . .

NB: mythcommflag and mythtranscode are both part of the frontend package
(if you are using ATRPMS), IIRC.  So you might have mythjobqueue, but
not actually be able to run anything useful...  I more-or-less just
install the frontend and backend everywhere, and then on the real
frontends I install all the plugins I need.

Also, mythjobqueue isn't a service, like mythbackend.  I had to stick a
line in /etc/rc.local to fire it up, and if the database isn't available
it won't restart.  So basically, I need to tweak my procedure a little
bit, but it works reasonably well right now.

> I'm also assuming that mythfilldatabase should run on the database 
> server, no?  Why load the backend with it, right?

Well, it could be run anywhere.  I think you can only take advantage of
the built-in support for running at the next suggested time on the
master backend.  If you did want to run it elsewhere, you could set up a
cron job - this is the one I used to use before I let MythTV handle
scheduling mythfilldatabase itself.

01 10 * * * sleep $(expr $RANDOM \% 14400) && mythfilldatabase >
/var/log/mythtv/mythfilldatabase.log 2>&1