I generally leave my torrents always seeding and it's currently downloading to the cache drive. However when the mover gets invoked everyday it doesn't move those completed downloads from the cache drive to the array because they are still seeding through rutorrent. Is there anyway I can tell mover to stop the rutorrent docker before it gets invoke and start it again once it finishes?

Not as such, but you could use the User Scripts plugin to schedule a script to run before mover to shutdown the docker, and at another one to later restart the docker (although you would have to guess at how longer mover needs and thus the timing of that one).

 

49 minutes ago, itimpi said:

Not as such, but you could use the User Scripts plugin to schedule a script to run before mover to shutdown the docker, and at another one to later restart the docker (although you would have to guess at how longer mover needs and thus the timing of that one).

Ya, worst case scenario I was planning on doing that. Would the script be as simple as

 docker stop rutorrent

and

docker start rutorrent

or do I need to do any checks before stopping/starting it?

Edited July 24, 20178 yr by bobokun

7 hours ago, itimpi said:

(although you would have to guess at how longer mover needs and thus the timing of that one).

Alternatively, you can disable mover from running automatically as per the directions here:  https://forums.lime-technology.com/topic/48707-additional-scripts-for-userscripts-plugin/#comment-483789 and then use user scripts to manage everything  (Note that this is a hack, and any changes to a setting in the scheduler will undo this change)

 

docker stop rutorrent
mover
docker start rutorrent

Although it would probably be good to specify the time to wait for a graceful shutdown of rutorrent before killing it:

docker stop -t 60 rutorrent

so that rutorrent won't have to recheck all of the files when it starts back up.

 

On 7/24/2017 at 5:40 PM, Squid said:

Alternatively, you can disable mover from running automatically as per the directions here:  https://forums.lime-technology.com/topic/48707-additional-scripts-for-userscripts-plugin/#comment-483789 and then use user scripts to manage everything  (Note that this is a hack, and any changes to a setting in the scheduler will undo this change)

 

docker stop rutorrent
mover
docker start rutorrent

Although it would probably be good to specify the time to wait for a graceful shutdown of rutorrent before killing it:

 

docker stop -t 60 rutorrent

so that rutorrent won't have to recheck all of the files when it starts back up.

 

I noticed that the script doesn't seem to execute the mover command.

Do you know what the full path of mover is?

This is my script:

 

#!/bin/bash
echo "Stopping rutorrent"
docker stop ----time=60 rutorrent
echo "executing mover"
mover
echo "Mover Complete. Starting Rutorrent docker"
docker start rutorrent
echo "Successfully started rutorrent"
 

 

Output Log:

Stopping rutorrent
rutorrent
executing mover
/tmp/user.scripts/tmpScripts/mover (Stopping dockers)/script: line 5: mover: command not found
Mover Complete. Starting Rutorrent docker
rutorrent
Successfully started rutorrent

 

Edited July 30, 20178 yr by bobokun

try changing "mover" to be /usr/local/sbin/mover

It worked. Thank you

So i am also trying to create a script that involves the mover, but can't get that part to work.  what is the line in your script the gets the mover to go exactly?

hm... dosent rutorrent have a move when completed plugin installed already?

I'm trying to use it with SABnzbd. When there are many files downloading my mover basically runs 24/7 as my download speed is about as fast as the mover.