Leerlauf erkennen, für den VDR / Idle detect for VDR

why not check with ip-ping ?

script examples found here:
http://www.ns4300n-info.de/forum/index.php?topic=106.0

I know that this is not a VDR specific (or streamdev-server) solution - but a beginning to work with...

joe

I think one thing is to grep ips from the log file - to know if a client is connected.

Feb  2 11:19:42 vdr vdr: [14054] Streamdev: Accepted new client (HTTP) 192.168.0.2:1599
Feb  2 11:19:42 vdr vdr: [14054] streamdev-server: Detaching current receiver
Feb  2 11:19:42 vdr vdr: [14054] streamdev: closing streamdev connection to 192.168.0.2:1599
Feb  2 11:19:42 vdr vdr: [14054] Streamdev: Accepted new client (HTTP) 192.168.0.2:1600
Feb  2 11:19:43 vdr vdr: [14054] streamdev-server: Detaching current receiver
Feb  2 11:19:43 vdr vdr: [14054] streamdev: closing streamdev connection to 192.168.0.2:1600

and check for timers here
/var/lib/vdr/timers.conf

or look at that shutdown script
http://www.vdr-wiki.de/wiki/index.php/Shutdown.sh

To check if the VDR currently records something you can also use the
svdrpsend.pl command

svdrpsend.pl NEXT rel

Seconds until next timer. A negative number indicates that a recording is done.

Best Regards
schneisa

Shouldn't streamdev report if its busy or not ? - if not there would be something important missing ... which i don't believe.

Also VDR knows if its busy, so you should configure IdleTimeout in VDR, thenVDR will request to shutdown the machine if idle.

Additional possibilities to check idle you have by using a shutdown script which is called right before going down. This scripts can block the shutdown or request to ask again in a few minutes. If you want to check for your clients with ipping, this could be done here as well, if you want to keep the server alive if a defined set machines is still around.