Delay startup when installed as service on WHS?
Posted: March 27th, 2011, 10:33 am
Hello
I have installed the beta (just updated to 0.6.0b4) as a service on my WHS - runs smoothly so far. Only problem sometimes is: for speed and HD-usage reasons, I have defined a download location for the download folder OUTSIDE the shared video folder, only the final extraction folder sits inside the Video-share on my WHS.
Since this download folder sits on a dedicated eSATA-disc (with its own drive letter T:\), sometimes when booting the WHS, the start of the SABnzbd-service is faster than Windows providing the external drive T:\ . Then, SABnzbd puts all downloads, even incomplete ones, into a download-folder it creates itself on d:\shares. That of course, I want to avoid.
Is there any way (and how can I reach that) to delay the start of both the SABnzbd- and the helper-service until WHS has fully booted and all drive letters are assigned? I think, a delay of 120 seconds after starting the booting would be appropriate to be on the safe side...
Thanks for the help!
I have installed the beta (just updated to 0.6.0b4) as a service on my WHS - runs smoothly so far. Only problem sometimes is: for speed and HD-usage reasons, I have defined a download location for the download folder OUTSIDE the shared video folder, only the final extraction folder sits inside the Video-share on my WHS.
Since this download folder sits on a dedicated eSATA-disc (with its own drive letter T:\), sometimes when booting the WHS, the start of the SABnzbd-service is faster than Windows providing the external drive T:\ . Then, SABnzbd puts all downloads, even incomplete ones, into a download-folder it creates itself on d:\shares. That of course, I want to avoid.
Is there any way (and how can I reach that) to delay the start of both the SABnzbd- and the helper-service until WHS has fully booted and all drive letters are assigned? I think, a delay of 120 seconds after starting the booting would be appropriate to be on the safe side...
Thanks for the help!