[mythtv] [bug?] slave backend expires current recording in process

[Torsten Schenkel]

Hi,

just finished setting up a slave backend on my workstation (and the
transgression to kernel 2.6. including ivtv and lirc, but that's another
story for another thread).

Now I noticed something strange:

Situation:

Both backends are recording, filesystem is 140GB/145GB filled.
Autoexpire kicks in and starts expiring, as it was doing all the time
and as expected. But what i didn't expect was it to stop the running
recording on the slave and expire it. There are about 20 programmes on
that disk that were to expire first, but it chose to expire the one in
progress.

With only the master up I never noticed such, but could say wich show
was to be expired next (well, obviously the oldest one with the
expirable flag set).

Maybe the problem was that the programme that was expired was the first
recording the slave did. Another thing I noticed: The expiring messages
show up on the slave's console/log not the master's.

Is this a (known) bug or am I missing something?

Torsten
-- 
Walkthrough: MythTV on Epia with PVR350 using Debian:
http://www-isl.mach.uni-karlsruhe.de/~hi93/myth/mythtv_debian_epia_pvr350_walkthrough