[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 5:44 PM
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] Multiple directories for MythTV recordings?
>
>
> Sounds like a neat solution. The only potential pitfall I can see is what
> will happen if the recording is being viewed while transfer is in
> progress.
> Also I cannot run slave backend on the nfs server (it's actually
> a winblows
> appliance, I've considered loading linux on it, but decided it is
> not worth
> the trouble and time to mess with it.) but I can set up a backend
> on one of
> the non-myth linux servers and access it via NFS. But would it
> not be easier
> to just update the storage path on same server and read it via NFS without
> need for second backend? Is the path global for the server or is
> it set per
> file?
>
> -M

Right; hence the second part of my message.  You don't actually need a
second backend.  All you need is an NFS server, and the approrpriate entries
in the Myth database to make it *think* that there's a second backend.
There is a setting "Master backend override", or something like that, that
tells the frontend to see if it can access the recording through its local
filesystem (even if that 'local filesystem' is really NFS).  If it can, it
will play directly from the filesystem without asking the backend to stream
the file.  This feature was initially put in to allow for the fact that
people with slave backends might want to access recordings that were hosted
on those slave backend machines even when the slave backend process wasn't
running on those machines.  So, basically, what you'd be doing is fooling
Myth into thinking that there was a slave backend, but that it just isn't
running at present.  Never mind the fact that it will *never* be running.
:-)

As for how to figure out a way to automate the file movement without
disrupting a potential in-progress playback... nothing comes immediately to
mind.

-JAC