No subject

has the mysql syntax that would tell Myth that all the recordings are now
owned by my master backend. I assume that once that change is made, Myth
will either auto-expire the recordings, or they'll be orphaned recording
entries that find_orphans.py can handle.

Is my assumption correct? And is this the best way to remove references to
my dead back end? The email thread that spawned the article is about a year
and a half old so I figured I'd see if there is anything better than what
I'm planning before breaking things. I'm running 0.25-fixes.

Thanks!

--bcaec517ab4c65f92404d2556d91
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>I had a slave backend die a few months ago and t=
hought I had cleaned up all the old recordings via find_orphans.py. However=
 that doesn&#39;t seem to be the case, as the script is &quot;sticking&quot=
; on one particular recording which it thinks is still on the old backend. =
I&#39;ve gone and deleted it from the GUI on one of my front ends but that =
didn&#39;t seem to help.<br>
<br></div>From the wiki page at <a href=3D"http://www.mythtv.org/wiki/Backe=
nd_migration">http://www.mythtv.org/wiki/Backend_migration</a> step 3 has t=
he mysql syntax that would tell Myth that all the recordings are now owned =
by my master backend. I assume that once that change is made, Myth will eit=
her auto-expire the recordings, or they&#39;ll be orphaned recording entrie=
s that find_orphans.py can handle.<br>
<br></div>Is my assumption correct? And is this the best way to remove refe=
rences to my dead back end? The email thread that spawned the article is ab=
out a year and a half old so I figured I&#39;d see if there is anything bet=
ter than what I&#39;m planning before breaking things. I&#39;m running 0.25=
-fixes.<br>
<br>Thanks!<br></div>

--bcaec517ab4c65f92404d2556d91--