Re: [vdr] read-only video directory

2013-03-08 Thread Peter Münster
On Fri, Mar 08 2013, Stephan Loescher wrote:

> No. The setup, timers, etc. from the server are all in the clients
> /video/server directory. The client does not use them, because they are not in
> its video-root-direcory.

In my case, the setup for client and server are the same, because I want
it this way. For now I'm lucky with this design, but whenever I'll need
different setups for client and server, I'll change that of course...


> When you use the suggested solution with unionfs, then the client uses the
> servers setup/timers/epg/etc. because it sees them in its /video-directory.

I'll keep this idea in my mind, and whenever I'll see, that my choices
are too limited, I'll reconsider your suggestions.

Thanks,
-- 
   Peter


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] read-only video directory

2013-03-08 Thread Stephan Loescher

Hi!


The VDR-client is started this way:
vdr -Pstreamdev-client -Pxineliboutput -v /video


Thanks, now I understand: /video is writable by vdr. I don't want
that: the client sees the same setup files (also the timers) as the
server, so the client would try to record the same as the server.


No. The setup, timers, etc. from the server are all in the clients
/video/server directory. The client does not use them, because they are 
not in its video-root-direcory.


When you use the suggested solution with unionfs, then the client uses 
the servers setup/timers/epg/etc. because it sees them in its 
/video-directory.


Regards,
Stephan.

--
loesc...@gmx.de
http://www.loescher-online.de/

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] read-only video directory

2013-03-08 Thread Peter Münster
On Fri, Mar 08 2013, Stephan Loescher wrote:

> The VDR-client is started this way:
> vdr -Pstreamdev-client -Pxineliboutput -v /video

Thanks, now I understand: /video is writable by vdr. I don't want
that: the client sees the same setup files (also the timers) as the
server, so the client would try to record the same as the server.
The client should not be able to record anything.

Thanks also to Steffen and Udo for your suggestions. I'm sure, that the
unionfs or aufs solutions would work, but I would like to keep things as
simple as possible: an ro-nfs-mount and a patched vdr.c work quite well.

I've just finished my vdr-setup: http://pmrb.free.fr/vdr/
Any comments are welcome!

-- 
   Peter


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] read-only video directory

2013-03-08 Thread Stephan Loescher

Hi!


The workaround I use is to mount the server in a subdirectory e.g. mount the
server-directory to /net/media/data/video/servervideo and start the client-vdr
like this:
vdr -Pstreamdev-client -Pxineliboutput -v/net/media/data/video


Unfortunately I don't understand. Could you please show examples?


My VDR-client has this directories:
/video
/video/server

I mount my VDR-server to /video/server, e.g.
mount -t nfs -o ro server:/video /video/server

The VDR-client is started this way:
vdr -Pstreamdev-client -Pxineliboutput -v /video

Regards,
Stephan.

--
loesc...@gmx.de
http://www.loescher-online.de/

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr