Hi Chuck <div class="gmail_quote">On Mon, Dec 27, 2010 at 21:16, Chuck Peters <<a href="mailto:cp@ccil.org">cp@ccil.org</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> I think it has been more than a week since the .24 fixes have been updated. Is something wrong with the autobuild process? </blockquote><div>Nope, upstream just hasn't been pushing changes to 0.24-fixes. You can check upstream commits at: <a href="https://github.com/MythTV/mythtv/commits/fixes%2F0.24/">https://github.com/MythTV/mythtv/commits/fixes%2F0.24/</a> As you can see, the last commit was on the 20th. If there was a source package build error it would show here: <a href="http://smithers.mythbuntu.org/~autobuild/weekly_mythtv.txt">http://smithers.mythbuntu.org/~autobuild/weekly_mythtv.txt</a> </div><div> If there was a binary package build error it would show here: <a href="https://launchpad.net/~mythbuntu/+archive/0.24/">https://launchpad.net/~mythbuntu/+archive/0.24/</a> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> I noticed something odd. A slave backend which does nothing more than commercial flagging showed up in the mythweb status as having recordings. But it appears to have old backup copies of the db. /var/lib/mythtv/recordings: total 39392 -rw-r--r-- 1 myth mythtv 13429394 2010-12-08 16:42 mythconverg-1264-20101208164228.sql.gz -rw-r--r-- 1 myth mythtv 13458426 2010-12-08 17:01 mythconverg-1264-20101208170102.sql.gz -rw-r--r-- 1 myth mythtv 13384230 2010-12-08 18:21 mythconverg-1264-20101208182050.sql.gz The times of the above files are right around when I upgraded from .22 to .23.1 and .24. The db isn't even on that machine so how did those get there? </blockquote><div>I think the backend backed them up when it updated the schema most likely. </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> So I decide I'll just shut off the slave backend and look at it more later... So I stop the service and add "exit 0" near the top of /etc/init.d/mythtv-backend. Yes it is a bad habit to edit start up scripts that way, but it worked for me, at least until now... exit 0 should stop it from starting... But no it starts right up. # service mythtv-backend start mythtv-backend start/running, process 16661 It shouldn't do that. What the ??? </blockquote><div>Don't modify anything in /etc/init.d/. That's a symlink to the upstart job compatibility script. If you want to disable an upstart service, rename the conffile in /etc/init/mythtv-backend.conf to /etc/init/mythtv-backend.conf.disabled or so. </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Thanks, Chuck -- Ubuntu-mythtv mailing list <a href="mailto:Ubuntu-mythtv@lists.ubuntu.com">Ubuntu-mythtv@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv</a> </blockquote></div> -- Mario Limonciello <a href="mailto:superm1@gmail.com" target="_blank">superm1@gmail.com</a>