[mythtv-users] Multiple directories for MythTV recordings?

[Joseph A. Caputo]

> -----Original Message-----
> From: mythtv-users-bounces at snowman.net
> [mailto:mythtv-users-bounces at snowman.net]On Behalf Of Max
> Sent: Thursday, July 31, 2003 4:18 PM
> To: MythTV Mailing List
> Subject: [mythtv-users] Multiple directories for MythTV recordings?
>
>
> Can MythTV use multiple directories or sub-directories for finding
> recordings? My Myth box has a relatively small drive and I would like to
> keep most of the recordings on my NFS filer, however recording straight to
> the filer proved to be too much for my setup (I am yet to figure
> out why) so
> I would like to be able to move the files without having to edit the db.


Don't know if this would work, but...

what if you ran a slave mythbacked process on your NFS server.  No tuner
card, so it won't try to record anything.  After the master backend has
recorded a program, you could copy the files over to the slave backend's
storage directory.  When the files are not found on the master backend, it
will (I think?) query the slave backend for them.  Should be not much load
on your NFS box, since all the slave backend would be doing is serving files
for playback (not encoding, decoding or GUI).  Actually, now that I think
about it, if you set it up so that your NFS-mounted storage directory has
the same path on both your frontend (NFS client?) and slave backend (NFS
server), when you play it back it will play directly from the NFS-mounted
storage directory, so you don't even need a second backend running.  The
only other thing you'd probably have to do is update the 'recorded' table
for the moved recordings to reflect the new storage host and path.  You
could easily automate both the NFS copy/move and the database update with a
script.

-JAC