[ATrpms-devel] Myth 0.17 backend init script problem

[commercial Voight]

I've got very similar problems here.

I've got my master backend (mythtv) with two tuners on it and PiP
works fine, so both tuners are working simultaneously.

I've also got my slave backend (gourd) with a single tuner in it. 
gourd can start mythfrontend and leech off mythtv, but I can't start
mythbackend via /sbin/service mythbackend start (same mysql errors
Jarod was getting) and I am unable to resolve it with the
.mythtv/mysql.txt file .

However, my problem gets worse from there.

I can start gourd (slave) mythbackend -d by hand, but it interferes
with mythtv (the master) as evidenced by mythweb (on mythtv [the
master]) status.php.  I was hoping somebody else could check their
status and tell me if they get a proto error like I do.

By the way, I had multiple backends working way back in the day with
cvs (prolly .11 or thereabouts), but since I've been using fresh fc3
installs (following your instructions, Jarod), I've had no luck with
the slaves.

Jeff...