Re: [vdr] read-only video directory

2013-03-10 Thread Udo Richter
Am 08.03.2013 19:35, schrieb Stephan Loescher:
 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.

Only until the first write, after that the client will continue with its
local writable copy.

It is generally possible (and in a network shared environment also a
good idea) to have config files in a different place, and just
recordings within /video. If you definitely want shared (read-only)
config files, I'd suggest using symbolic links, like
/etc/vdr/channels.conf - /net/media/data/vdr-config/channels.conf.
Solves a lot of problems, like clients trying to record the same as the
server because of same timers.conf, or not having to configure
streamdev-client on the server.

Cheers,

Udo


___
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


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-07 Thread Steffen Barszus
2013/3/6 Peter Münster pmli...@free.fr:
 On Wed, Mar 06 2013, Stephan Loescher wrote:

 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


 On Wed, Mar 06 2013, Udo Richter wrote:

 You can always mount an unionfs or aufs on top of the read only mount,
 and redirect all write access to a local disk or ram disk. That way VDR
 will be able to write its status files without changing the source file
 system.

 Hi Stephan and Udo,

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

 I have for example this directory:
 /net/media/data/video/Pippi-geht-von-Bord/2010-07-31.06.55.50.99.rec
 The slave (nfs-client) should read it, but it should not write anything
 to this directory (or its parents). Is this possible with your
 solutions?


With a union filesystem you can mount the lower level read only and
have an upper layer where changes get stored.
So yes - the master file system will for sure not be touched and you
can keep VDR as is and keep full functionality.

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


Re: [vdr] read-only video directory

2013-03-07 Thread Udo Richter
Am 06.03.2013 21:56, schrieb Peter Münster:
 On Wed, Mar 06 2013, Stephan Loescher wrote:
 On Wed, Mar 06 2013, Udo Richter wrote:
 You can always mount an unionfs or aufs on top of the read only mount,
 and redirect all write access to a local disk or ram disk. That way VDR
 will be able to write its status files without changing the source file
 system.
 
 Hi Stephan and Udo,
 
 Unfortunately I don't understand. Could you please show examples?
 
 I have for example this directory:
 /net/media/data/video/Pippi-geht-von-Bord/2010-07-31.06.55.50.99.rec

Just improvising, haven't tested it, but should give you a hint how to
do it:

- assuming /net/media is an NFS mount or similar
- create a folder /net/media-tmp (optionally mount an tmpfs on it)
- create a folder /net/media-rw
- mount -t aufs -o br:/net/media-tmp:/net/media aufs /net/media-rw

Now you have a virtual copy of /net/media in /net/media-rw, fully
writeable, where all write access goes to /net/media-tmp instead,
leaving /net/media untouched. You can play back
/net/media-rw/data/video/Pippi-geht-von-Bord/2010-07-31.06.55.50.99.rec
just as before, you can even delete it, but the recording will only
disappear within /net/media-rw, the original copy in /net/media stays
untouched.

Cheers,

Udo


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


Re: [vdr] read-only video directory

2013-03-06 Thread Peter Münster
On Wed, Mar 06 2013, VDR User wrote:

 With no bad side effects?

So far only some error messages in the log-file, whenever vdr tries to
write something. Quite reasonable for me.

-- 
   Peter


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


Re: [vdr] read-only video directory

2013-03-06 Thread Stephan Loescher

Hi!

Am 03/05/13 10:35, schrieb Peter Münster:


How is it possible, to mount the video directory in read-only mode?

I want to use a slave vdr like this:

vdr -Pstreamdev-client -Pxineliboutput -v/net/media/data/video

But it does not work, because /net/media/data is mounted read-only.


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

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-06 Thread Udo Richter
Am 05.03.2013 10:35, schrieb Peter Münster:
 How is it possible, to mount the video directory in read-only mode?
 I want to use a slave vdr like this:
 vdr -Pstreamdev-client -Pxineliboutput -v/net/media/data/video
 But it does not work, because /net/media/data is mounted read-only.
 The slave vdr should not write anything, just read the recordings.

You can always mount an unionfs or aufs on top of the read only mount,
and redirect all write access to a local disk or ram disk. That way VDR
will be able to write its status files without changing the source file
system.


Cheers,

Udo


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


Re: [vdr] read-only video directory

2013-03-06 Thread Peter Münster
On Wed, Mar 06 2013, Stephan Loescher wrote:

 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


On Wed, Mar 06 2013, Udo Richter wrote:

 You can always mount an unionfs or aufs on top of the read only mount,
 and redirect all write access to a local disk or ram disk. That way VDR
 will be able to write its status files without changing the source file
 system.

Hi Stephan and Udo,

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

I have for example this directory:
/net/media/data/video/Pippi-geht-von-Bord/2010-07-31.06.55.50.99.rec
The slave (nfs-client) should read it, but it should not write anything
to this directory (or its parents). Is this possible with your
solutions?

TIA,
-- 
   Peter


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


[vdr] read-only video directory

2013-03-05 Thread Peter Münster
Hi,

How is it possible, to mount the video directory in read-only mode?

I want to use a slave vdr like this:

vdr -Pstreamdev-client -Pxineliboutput -v/net/media/data/video

But it does not work, because /net/media/data is mounted read-only.

The slave vdr should not write anything, just read the recordings.

TIA for any hints,
-- 
   Peter


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


Re: [vdr] read-only video directory

2013-03-05 Thread VDR User
On Tue, Mar 5, 2013 at 1:35 AM, Peter Münster pmli...@free.fr wrote:
 How is it possible, to mount the video directory in read-only mode?

 I want to use a slave vdr like this:

 vdr -Pstreamdev-client -Pxineliboutput -v/net/media/data/video

 But it does not work, because /net/media/data is mounted read-only.

 The slave vdr should not write anything, just read the recordings.

IIRC it's not possible, IIRC... A workaround is to use the mplayer
plugin and add your recordings dir to the sources list. Then make the
recordings dir /tmp or something. Maybe you could even use /dev/null,
I dunno.

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


Re: [vdr] read-only video directory

2013-03-05 Thread Peter Münster
On Tue, Mar 05 2013, VDR User wrote:

 A workaround is to use the mplayer plugin

I prefer the VDR interface. Finally it's very easy:

I've just deleted the lines

--8---cut here---start-8---
  if (!DirectoryOk(VideoDirectory, true)) {
 fprintf(stderr, vdr: can't access video directory %s\n, VideoDirectory);
 return 2;
 }
--8---cut here---end---8---

in vdr.c and now it works as expected...  :)

-- 
   Peter


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


Re: [vdr] read-only video directory

2013-03-05 Thread VDR User
On Tue, Mar 5, 2013 at 4:23 PM, Peter Münster pmli...@free.fr wrote:
 A workaround is to use the mplayer plugin

 I prefer the VDR interface. Finally it's very easy:

 I've just deleted the lines

 --8---cut here---start-8---
   if (!DirectoryOk(VideoDirectory, true)) {
  fprintf(stderr, vdr: can't access video directory %s\n, 
 VideoDirectory);
  return 2;
  }
 --8---cut here---end---8---

 in vdr.c and now it works as expected...  :)

With no bad side effects?

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