[mythtv-users] BUG? auto-expire with slave backends

[Chad J McQuinn]

I am using the latest (as of ~2 days ago) CVS, but I am sending this to 
-users because I believe it happens with release versions as well.

I have a master + slave backend setup. Most shows I set to keep five 
episodes then auto-expire, deleting the oldest show. This works 
correctly for shows stored on the master backend, but shows on the 
slave backend are not being deleted. They *are* removed from the 
database; I finally figured out what was happening when I started to 
run out of space.

Running contrib/myth.rebuildatabase.pl on the slave backend reveAled 
that every show that was supposedly autoexpired was actually still 
there in the file system. This morning I finally caught the master 
backend saying this:

2004-05-06 02:31:27 Expiring "Chappelle's Show" from 
2004-04-27T23:30:00, too many episodes.
2004-05-06 02:31:27 Strange, file: 
/mnt/video/1050_20040427233000_20040428000000.nuv doesn't exist.
2004-05-06 02:31:27 Expiring "Scrubs" from 2004-04-13T21:31:00, too 
many episodes.
2004-05-06 02:31:27 Strange, file: 
/mnt/video/1012_20040413213100_20040413220000.nuv doesn't exist.

Of course these files are actually both on the slave, which is why it 
didn't find them.

Is anyone else having problems with auto-expire and a slave backend?

-Chad