oztoppy Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
keith_leitch

Senior Member
Registered:
Posts: 525
Reply with quote  #1 
I am wondering if there is a way around the "three-minute rule."

In the event of the PVR starting due to a scheduled timer, TMSServer will not launch until three minutes have elapsed. I understand the rationale for this, and it makes sense: conserving resources when no human may be involved in the PVR's use.

However, I would prefer that it launch unconditionally, without waiting three minutes.

I am currently using XStart to launch it right away, then wait three minutes and launch it again. This works, but, on a manual start, results in two instances of the TAP running. If there is no other way around this, I will look at using the Script TAP to first determine whether TMSServer is already running before invoking the second launch. (Or, could I do the same thing by adding to a script in TMSClient?)
0
DeltaMikeCharlie

Mostly Harmless
Registered:
Posts: 235
Reply with quote  #2 
Version 1.3 has a config item that allows startup at every boot.  What version are you running?
0
keith_leitch

Senior Member
Registered:
Posts: 525
Reply with quote  #3 
1.20-Dev1. Where can I find the newer version?
0
DeltaMikeCharlie

Mostly Harmless
Registered:
Posts: 235
Reply with quote  #4 
Attached.

 
Attached Files
zip TMSServer-v1.3.zip (120.68 KB, 3 views)

0
keith_leitch

Senior Member
Registered:
Posts: 525
Reply with quote  #5 
Thanks. Installed and running. This will make a huge difference.

I found this link on your site to 1.20 Dev3. However, it reports as Dev2 when I run it.

http://deltamikecharlie.yolasite.com/resources/TMSServer%2BTMSClient.zip


0
keith_leitch

Senior Member
Registered:
Posts: 525
Reply with quote  #6 
I've noticed, twice now, that the latest version you provided still does not start with the PVR launches a recording. I have option 06 set to EVERY BOOT, but it still starts only when I manually start the PVR.
0
keith_leitch

Senior Member
Registered:
Posts: 525
Reply with quote  #7 
For the time being, to ensure that TMSServer eventually starts after every boot, I have added the following lines to the end of TMSClient's NFS file:

Code:

sleep 3m
/mnt/hd/ProgramFiles/Scripts/starttaponce /mnt/hd/ProgramFiles/XStart/TMSServer.tap

exit



(The call is to a tested external script that checks if a TAP has started, then starts it only in the case that it is not already running).

DMC, do you have any concerns that I may have missed about modifying NFS in this way?

0
keith_leitch

Senior Member
Registered:
Posts: 525
Reply with quote  #8 
An interesting side-effect of this, that I don't understand.

After modifying the NFS file as above, TMSServer now launches on every boot. It either launches right away on a manual start, or, in the case of a recording, three minutes later from the NFS script. I have confirmed that it is running, and that it starts my scripts, etc.

The strange thing is that a client Topfield cannot connect to it through TMSClient if TMSServer starts ater booting for a recording. I've tried this on five separate occasions, now, with the same result; if my lounge room 2460 comes on due to a recording, my bedroom 7160 cannot find it, even though TMSServer is running. Only if I manually intervene--either reboot the 2460, or stop and restart TMSServer on it--does the client machine connect a mount-point.

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.