1. I have not yet upgraded to latest version as I don't want to take a risk having unstable envirounment again (this was true for 1.92 up to 2.04). I have noot seen new features introduced worth upgrating. Is there a compatibility issue of my script with 2.12? If yes - this will push me towards.

2. New versions are definately made to deliver new features and fix bugs, but it also use to bring new bugs. I would say that you can call release as good or bad analyzing ratio of fixed old bugs/introduced new bugs. As far I know by reading historical data - Transmission was getting better and better untill 1.92 when the number of crashes got much higher rate comparing to new features. For some reason, many users, including myself, have found versions 1.92-2.03 (not sure about next) as not worth upgrading from 1.91 as they have reduced total stable working time of daemon. No matter how cool new features are - if the software keeps crashing - you are not happy. It will change someday and there will be (if not already) new stable version worth upgrading. I could check not earlier than late December.

Pavel

1. Do you have intention to make your script compatible to the latest Transmission version?
2. Are the latter versions of transmission really better than the previous ones, because I always thought that point of making new version is that it brings fixes and better resource control?

Thanks in advance

1. I was roll-back to 1.91 version of transmission.
2. I was switched off all cron activity concerned to transmission.

As result I have stable system during last 2 days. That is record for long-long time before.
Even my big torrent with 140 GB size is already checked and continues downloading process. Thanks God seeders are still alive! :-)

Maybe this kind of solution can help someone from this thread.

There is no need to use any external permission correction since there is a built-it feature of Transmission Daemon to set
umask to every file it creates. More details you can find here next to umask property.

So:
chmod 755 (umask 022) would be 18 in json
chmod 775 (umask 002) would be 2 in json
chmod 777 (umask 000) would be 0 in json

I recommend using 0 and enjoy your torrents :)

Pavel

I found that the ratio was the issue :)
I disabled seeding in my json-file because I didnt know what this was :) I changed the values and it works!

I still have one question :D:

I want to move the file to a folder and change the "chown" and "chmod": chmod 775 and chown root:www-data
The moving part is already made by you :):):)
How do I fix the chown and chmod part?

tx!!

Check here, here, here or search for "transmission_1.91-1_arm.ipk"

Pavel

I am glad you have fixed your issue #1. Regarding issue #2 - script is not removing your completed torrent from list as it did not hit Max Ratio (0.0777 out of 2.0000 seeded). You can see UNDER status next to your torrent, once it hits or overseeds - it will show OVER and it will then be removed.
The question is "Why it is STOPPED and not SEED". Have you set MAX_TO_SEED=0 ??? This is not good :)

You have 2 options:
1) Being Nice - set MAX_TO_SEED to reasonable number greater than 0 and seed downloaded torrent to hit ratio 2.0 and then script will stop and remove torrent from list.
2) Being Selfish - Edit Transmission config and set "ratio-limit" to something less than 1 or even 0, so that once torrent is downloaded it will be over limit rightaway.

Please choose option 1 :)

Pavel

Version is 2.04. I solved issue 1 -> logfile dir. was incorrect :) I hope this stays stable…

Issue 2: The file is paused but not removed…

transmission queue
watch: transmission-daemon is running
awk: warning: escape sequence '\)' treated as plain ')'
1 069% DOWNLOAD 0.0728 UNDER
2 064% DOWNLOAD 0.1267 UNDER
3 012% DOWNLOAD 0.0452 UNDER
4 100% STOPPED 0.0777 UNDER
Max Ratio: 2.0000
Downloading: 3 (max 30)(to start 27)
Seeding: 0 (max 0)(to start 0)
Stopped: 1 and Stopped on 100: 1
Torrent IDs to Stop:
Torrent IDs to Start:
Torrent IDs to Remove
Execution Time: 2 secs.

The file is in my complete folder but stays in pause in the list…

1) Lets start with Transmission start problem. I have tested this script only on transmission daemon versions 1.91 and 2.03. What version are you using? You can find out by running the following command:

transmission-daemon -V

2) Removing torrent issue. The main logic to move and remove torrent from the list is:

• Torrent has to be 100% downloaded
• Torrent has to seed as much as reaching MAX RATIO (by default 2.0)
• Once it is seeded over MAX RATION script will attempt to:
• * stop (pause) torrent
• * move data to Complete folder
• * next run it will check if completed torrents are located in Completed folder and it it is there (meaning it was successfully moved) - it will remove torrent from list

First issue might affecting the second one, so please start with issue 1)
If you can not fix it - send me PM with exact script you have.

Cheers,
Pavel

Let me separate scenarios into 2 parts:

1) Watch - ensuring Transmission is responsive.
In this case, script is checking if process is in memory and if it is not - starts it.
If it is in memory - scripts attempts to receive transmission session information - the most lightweighted command.
If transmission-remote return an error - script will send HUP signal via killall to force daemon restart via internal routin.
If transmission-remote does not return an error - script assumes it is OK.
This watch function will not attempt to completely stop and start daemon as HUP in most cases will help, but in minor cases it will continue to hang untill next scheduled "2 hours" restart.

2) Stop/Restart procedure
This routin is called only using parameters stop/restart.
In this case, script will attempt to gently kill daemon letting it close all the threads taking its time. Every 5 seconds script will check if daemon process is still in memory and if it still is - will send another gently kill command and so on.
If script has counted more than 20 times (5 seconds hold after each) and daemon is still running - it will stop being nice and will send force kill command. It will again start checking process and keep sending force kill every 3 seconds for a while and then leave it as is.

The reason why script is so patient in the first place is to mitigate chances "breaking hash" and thus having transmission re-check.

Your script is doing similar things. I hope I have answered your question. If not - please expand your question.

Cheers,
Pavel.

I installed the script and I love it. Although I have a few issues:

- "transmission start" seems not to work. It always tells me that "usage: transmission-daemon [options]" and it does not start …

- when a torrent is finished, the file is moved to the correct directory and the dowload is "paused", but the torrent is not removed.

tx for helping me!

Thank you for your question. The answer is simple:
When the daemon is not responding - it is already late - restart is a reactive measure to restore functionality and in THIS case - it will not terminates gentely and Transmission will re-check active torrents once will be started again - takes a lot of time.
Restarting daemon while it is still responsive is a proactive measure that will not lead to re-check active torrents once daemon will be back, while it will delay the time of freeze. Wasting 5 minutes every 2 hours for restart in long run is better than waiting for transmission to freeze and let it re-check active torrents that is taking ages on big files. My tests showed that in 2-3 minutes after restart initiated - daemon is again responding and in next 2 minutes - all active torrents are back on full speed to download and seed. NO RE-CHECKS as it has terminated gentely before that!

The bungle include "watch" function (also triggered with "queue" function) - that is checking if service is responding and if not - is sending HUP signal that force internal daemon routin to read config file that is helping in most cases to release the freeze.

Hope my logic is clear. Cheers.

Here is a snippet from my transmission manager script:

# ************ # Let's see if the process fails to respond echo Connecting to service RESPONSE=$($REMOTE -l 2>&1 | awk '{print $4}' | grep Error) if [ "$RESPONSE" != "" ]; then echo Transmission returned error, restarting service $INIT rm /tmp/checktransmission exit fi RESPONSE=$($REMOTE -l) if [ "$RESPONSE" = "" ]; then echo Transmission returned error, restarting service $INIT rm /tmp/checktransmission exit fi

140 GB torrent!!!111one? :))) Wow! I can not imagine how long it will take to check 140 GB on MBWE. I have to admit - I assumed 2 hours restart frequency is optimal based on my personnal usage, however in your case - 2 hours should be increased to way higher value.

Another question is why Transmission wants to check this big torrent in the first place. It will not re-check torrenet if Transmission has gentley terminated. So if if wants to check - you are screwed :) and have to spend numerous hours to let it complete. This process should not be interrupted, because it will start from the very beginning. I recommend simply commenting cron line that is rebooting daemon and when it is completed - enable it again.

Cheers,
Pavel.

1) Regarding CRON job - I recommend trying the following command (perhaps after installing cron package):

crontab -e

2) Regarding starting automatically after boot - Yes, it is designed to start Transmission Daemon automatically after boot. If it does not start I recomend the following troubleshooting steps:

• Enable startup:

transmission startup on

• Check locations in the script - make sure they are valid to your system. If you figured out they are wrong - correct them and run install command once again. Then reboot to test.

Hope it helps. Cheers.
Pavel

How I can fix this issue?

Maybe the best way is to stop all active torrents. Launch transmission in usual mode and give some time to verify all big torrent data.

Also am I correct in the assumption that your script starts automatically after I reboot my white light mbw together with all the other things I set up too boot with?

Thanks for helping!

Thank you for your detailed explanations. Now it looks more realistic to solve all mine troubles with torrents download.
So, now I finished with settings and I was follow to your advice.

Time will tell. :-)

Please do not be confused about install feature of this script - it does NOT install Transmission Daemon itself, it only installs startup/shutdown scripts.
I have let user to install Transmission Daemon himself beforehand since I do not posess the architecture of your system and package may vary.

Please use another instructure to download and install Transmission Daemon packages on your system (I recommend 1.91 so far as the seniorest most stable version)

After you have your Transmission installed - you may find advantage of using this manage script.
Cheers.

On your questions, I believe:
1) If Transmission daemon is checking torrents after each reboot - it means it did not terminates itself nicely on shutdown. Your second question actually proves it as you even can not killall transmission-daemon process. Keep in mind that if transmission crashed or killed - it will practically start checking only those torrents that were in download state before it crached, so the less torrents in "Download" state you have - the sooner it will start downloading again.
Moreover, original shutdown script was only waiting for 5 seconds for gentle shutdown before attempting to force kill transmission daemon. I found it too agressive and changed timeout to 100 seconds for gentle shutdown and timeout for killall to 30 seconds - this however will delay rebooting, but increase a chance that transmission will not re-check your torrents.

2) When I first noticed that Transmission crashed my WBME on regular basis - I spent a lot of time finding "a fix". When I last checked 2 weeks ago - fix was not yet available. Transmission was not working more than a day on my system, and on active torrents utilization- crached every 2-3 hours.
I have solved my headache with several steps:

• I have set speed limints to download 3 mb/s and upload 1 mb/s - prolonged time of life
• I kept maximum torrents in download state under 2-3 - decreased time of checking after crash
• I set CRON job to restart transmission daemon every 2 hours - this is the most affective step strategically. Why? Read below:

When you restart transmission when it is working fine (read: not yet crashed ;-) ) - it will take not more than 3-5 minutes to stop, start restore your bandwith activity. No file checking will be applied. While if you will let it work without restarts - it will crash sometime and you will be waiting ALOT for daemon to check the file before it will continue downloading. What is less painfull? I made my choice to regular restarts and I don't know pain anyore. I strongly recommends applying proposed CRON jobs in script.
Cheers.

Pavel

I can install transmission with this script :(
I use install information but nothing. After transmission install command I see nothing, snif :'(

I have desinstall old version of transmission before try this new installation

I need some help.
Thanks :-)

But I have two problem:

1) Transmission checks undone torrents after each reboot;
2) Transmission daemon crashed after 18-20 hours of stable works. System even can't remove process by killall command under root account.

Do you have any ideas about reasons for these two issues?

I would like to share with you script that I was working on time-by-time for past month or two. I was originally using numerous scripts I found over the web to do what I need, but non of them were able to manage Transmission queue on My Book due to the bug related to this system that prevent showing torrent status (Stopped/Download/Seed) correctly from transmission-remote list output.
So I start developing my own script to use debug mode of Transmission Remote and parse JSON within bash to properly identify torrent state and to apply manage logic. Finally I end-up with single script to do everything I would think of someone would need from Transmission.

Let's call it Transmission All-in-One manage script. Version 1.0

Features:

• Install/UnInstall startup and shutdown scripts (overwrites default Optware scripts)
• Enable/Disable startup of Transmission on boot as check flag
• Start/Stop/ReStart of Transmission
• Stability fix by setting EVENT_NOEPOLL=1; EVENT_NOEVPORT=1; EVENT_NODEVPOLL=1
• Updating Blocklist from download.m0k.org
• Edit Transmission config file and if changed force Transmission to re-read config file
• Watch Transmission and Restart if not responding
• Status of torrents in Transmission Remote native output format
• Torrents Queue manage:
  • start and stop torrents according to MAX_TO_DOWNLOAD and MAX_TO_SEED values
  • stop seeding once Max Ratio is reached
  • respects ratio-limit from Transmission config file
  • move torrent data to Complete folder once enough seeded and remove from Transmission list if succeeded
  • use minimum calls to Transmission Remote
  • watch check included
  • overcome torrent Status bug on WD MyBook system by parsing JSON instead of regular list output

Installation:

cd /opt/bin wget -O transmission http://pavel.kuzub.com/scripts/transmission chmod a+x transmission transmission install

CRON Jobs:

#Transmission Queue Control every 5 minutes */5 * * * * /opt/bin/transmission queue #Transmission Restart every 2 hours as stability workaround 0 */2 * * * /opt/bin/transmission restart

Usage:

# Start Transmission transmission start # Stop Transmission transmission stop # Call Boot procedure transmission startup # Enable starting Transmission on boot procedure transmission startup on # Disable starting Transmission on boot procedure transmission startup off # Show Transmission Remote List transmission status # Restart Transmission transmission restart # Open VI (or another editor) to edit settings.json transmission edit # Watch Transmission and kick if needed transmission watch # Queue manage (for CRON) transmission queue # Install startup and shutdown scripts transmission install # Uninstall startup and shutdown scripts transmission uninstall # Show commands transmission usage

Script Code:

#!/bin/sh # # Transmission All-in-One manage script. Version 1.00 # Tested with Transmission Daemon versions 1.90 and 2.03 on WD My Book World Edition White Light # Script by Pavel Kuzub. Some code is re-used from their respective owners. # On embedded systems consider installing the following packages: # ipkg install busybox-base # ipkg install busybox-links # # Full list of dependency is not available # # Installation: # wget -O transmission http://pavel.kuzub.com/scripts/transmission # chmod a+x transmission # transmission install # # Cron Jobs: # #Transmission Queue Control every 5 minutes # */5 * * * * /opt/bin/transmission queue # # #Transmission Restart every 2 hours as stability workaround # 0 */2 * * * /opt/bin/transmission restart # USAGETEXT="Usage: $0 (start|stop|startup|startup on|startup off|status|restart|edit|watch|queue|install|uninstall|usage)" # start_time=$(date +%s) # Change below folders to match your own system folders # Log file for DEBUG LOGFILE=/DataVolume/Download/transmission-daemon.log # Move downloaded and fully seeded files to Completed folder COMPLETED_DATA_FOLDER=/DataVolume/Download/!Completed # Location of init.d folder on your system INITDIR=/etc/init.d # If using authentication specify Login and Pass REMOTE_LOGIN=admin REMOTE_PASS=password # Maximum simultaneous torrents in Download state MAX_TO_DOWNLOAD=3 # Maximum simultaneous torrents in Seed state MAX_TO_SEED=25 # Enable moving torrent data after reaching Max Ratio. Value 1/0 MOVE_AFTER_COMPLETE=1 # Enable dump to log file. Value 1/0 DEBUG=1 # # More system related options EDITOR=vi prefix="/opt" INITSTARTSCRIPT=${INITDIR}/S90transmission INITSTOPSCRIPT=${INITDIR}/K10transmission PATH=${prefix}/bin:${prefix}/sbin:/sbin:/bin:/usr/sbin:/usr/bin DAEMONNAME=transmission-daemon REMOTENAME=transmission-remote DAEMON=${prefix}/bin/${DAEMONNAME} REMOTE=${prefix}/bin/${REMOTENAME} CONFIGDIR=${HOME}/.config/transmission-daemon CONFIGFILE=${CONFIGDIR}/settings.json NOSTARTUPFILE=${CONFIGDIR}/.transmissionNoStartup test -x $DAEMON || exit 0 if [ -z "$1" ] ; then case `echo "$0" | sed 's:^.*/\(.*\):\1:g'` in S??*) rc="startup" ;; K??*) rc="stop" ;; *) rc="usage" ;; esac else rc="$1" fi myecho() { curtime=`date +"[%H:%M:%S:000]"` echo "$curtime $1" if [ ${DEBUG} -eq 1 ]; then echo "$curtime $1" >>$LOGFILE fi } start() { if [ -n "`pidof $DAEMONNAME`" ]; then myecho "$DAEMONNAME is already running." else cd ${CONFIGDIR}/blocklists if [ $? -eq 0 ]; then find . -mtime +4 -type f -name level1 -exec rm {} \; if [ ! -f ${CONFIGDIR}/blocklists/level1 ]; then # update blocklist myecho "Updating blocklist, ~4MB" wget -q -O level1.gz http://download.m0k.org/transmission/files/level1.gz if [ -f level1.gz ]; then gunzip level1.gz if [ $? -eq 0 ]; then chmod go+r level1 else rm -f level1* fi fi fi cd - 2>&1 >/dev/null fi myecho "Starting Torrent client: $DAEMONNAME" EVENT_NOEPOLL=1; export EVENT_NOEPOLL EVENT_NOEVPORT=1; export EVENT_NOEVPORT EVENT_NODEVPOLL=1; export EVENT_NODEVPOLL nice -n 19 $DAEMON -g ${CONFIGDIR} -e $LOGFILE fi } watch() { if [ -n "`pidof $DAEMONNAME`" ]; then echo "Watch: $DAEMONNAME is running" $REMOTE -n $REMOTE_LOGIN:$REMOTE_PASS -si > /dev/null || killall -HUP $DAEMONNAME else start fi } stop() { if [ -n "`pidof $DAEMONNAME`" ]; then myecho "Stopping Torrent client: $DAEMONNAME" n=1 while true; do killall $DAEMONNAME 2> /dev/null sleep 1 [ ! -n "`pidof $DAEMONNAME`" ] && break myecho "Waiting for another 5 seconds. Attempt $n" sleep 4 [ $n -gt 20 ] && break let n+=1 done n=1 while true; do killall -9 $DAEMONNAME 2> /dev/null sleep 1 [ ! -n "`pidof $DAEMONNAME`" ] && break sleep 2 [ $n -gt 10 ] && break let n+=1 done if [ -n "`pidof $DAEMONNAME`" ]; then myecho "Termination of $DAEMONNAME was not successful, it keeps running" else myecho "$DAEMONNAME terminated successfuly" fi else myecho "$DAEMONNAME already stopped" fi } startup() { if [[ -e $NOSTARTUPFILE ]]; then echo "Transmission Daemon disabled on startup" else start fi } startup_on() { echo "Enabling Transmission Daemon on startup" if [[ -e $NOSTARTUPFILE ]]; then rm "$NOSTARTUPFILE" fi } startup_off() { echo "Disabling Transmission Daemon on startup" touch "$NOSTARTUPFILE" } edit() { MD5BEFORE=`cat "$CONFIGFILE" | md5sum` myecho "Starting $EDITOR to edit ${CONFIGFILE}" $EDITOR "${CONFIGFILE}" MD5AFTER=`cat "$CONFIGFILE" | md5sum` if [ "$MD5BEFORE" = "$MD5AFTER" ]; then echo "No changes to config file" else myecho "Sending SIGHUP to Transmission to reload config file" killall -HUP $DAEMONNAME 2> /dev/null fi } status() { $REMOTE -n $REMOTE_LOGIN:$REMOTE_PASS -l } install() { echo "Creating link: $INITSTARTSCRIPT" ln -s -f "$0" "$INITSTARTSCRIPT" chmod a+x "$INITSTARTSCRIPT" echo "Creating link: $INITSTOPSCRIPT" ln -s -f "$0" "$INITSTOPSCRIPT" chmod a+x "$INITSTOPSCRIPT" } uninstall() { echo "Removing: $INITSTARTSCRIPT" rm "$INITSTARTSCRIPT" echo "Removing: $INITSTOPSCRIPT" rm "$INITSTOPSCRIPT" } queue() { MAX_RATIO=$(cat "${CONFIGFILE}" | grep \"ratio-limit\": | tr -dc '[.0-9]') JSON=`$REMOTE -n $REMOTE_LOGIN:$REMOTE_PASS -b -l 2>&1 | grep "{\"arguments\":{\"torrents\":"` #Build data matrix in internal format. It will be used for all further references torrentStatus=`echo $JSON | awk '{n=split($0,a,"["); text=""; for (i=2;i<=n;i++) text=text a[i]; print text} ' | awk '{n=split($0,a,"]"); text=""; for (i=1;i<n;i++) text=text a[i]; print text} ' | sed -e 's/[{]//g' | awk -v max_ratio="$MAX_RATIO" '{n=split($0,a,"\},"); for (i=1;i<=n;i++) { id="";left="";total="";status="";ratio="";percent="" m=split(a[i],b,",") for (t=1;t<=m;t++) { o=split(b[t],c,":") if (c[1]=="\"id\"")id=c[2] if (c[1]=="\"leftUntilDone\"")left=c[2] if (c[1]=="\"sizeWhenDone\"")total=c[2] if (c[1]=="\"status\""){ if (c[2]=="1") status="CHECK_WAIT" else if (c[2]=="2") status="CHECK" else if (c[2]=="4") status="DOWNLOAD" else if (c[2]=="8") status="SEED" else if (c[2]=="16") status="STOPPED" else status=c[2] } if (c[1]=="\"uploadRatio\"")ratio=c[2] } if (left==0) percent=100 else if (total>0){ percent=((total-left)/total)*100 split(percent,percent_split,".") percent=percent_split[1] } else percent=000 for (l=length(percent);l<3;l++) percent="0"percent if(ratio>=max_ratio) ratio_status="OVER" else ratio_status="UNDER" print id" "percent"% "status" "ratio" "ratio_status }}' | sed -e 's/[}]//g'` #Make status calculations count_download=`echo "$torrentStatus" | grep -e 'DOWNLOAD' -e 'CHECK' | wc -l` count_seed=`echo "$torrentStatus" | grep SEED | wc -l` count_stopped=`echo "$torrentStatus" | grep STOPPED | wc -l` count_stopped_100=`echo "$torrentStatus" | grep STOPPED | grep 100% | wc -l` if [ $MAX_TO_DOWNLOAD -gt $count_download ] then count_download_to_start=$(($MAX_TO_DOWNLOAD - $count_download)) else count_download_to_start=0 fi if [ $MAX_TO_SEED -gt $count_seed ] then count_seed_to_start=$(($MAX_TO_SEED - $count_seed)) else count_seed_to_start=0 fi #Echo data for user echo "$torrentStatus" echo "Max Ratio: $MAX_RATIO" echo "Downloading: $count_download (max $MAX_TO_DOWNLOAD)(to start $count_download_to_start)" echo "Seeding: $count_seed (max $MAX_TO_SEED)(to start $count_seed_to_start)" echo "Stopped: $count_stopped and Stopped on 100: $count_stopped_100" #Logic part downloads_to_stop=`echo "$torrentStatus" | grep DOWNLOAD | sort -r -k 2,2 | tail -n +$((MAX_TO_DOWNLOAD+1)) | \ awk '{print $1;}' | tr '\n' ',' | sed 's/\(.*\)./\1/'` seeds_to_stop=`echo "$torrentStatus" | grep SEED | sort -r -k 4,4 | tail -n +$((MAX_TO_SEED+1)) | \ awk '{print $1;}' | tr '\n' ',' | sed 's/\(.*\)./\1/'` #check length and assign delimeter if [ ${#downloads_to_stop} -gt 0 -a ${#seeds_to_stop} -gt 0 ] then delim_to_stop="," else delim_to_stop="" fi ids_to_stop="$downloads_to_stop$delim_to_stop$seeds_to_stop" echo "Torrent IDs to Stop: $ids_to_stop" downloads_to_start=`echo "$torrentStatus" | grep STOPPED | grep -v 100% | sort -k 2,2 | tail -n $((count_download_to_start)) | \ awk '{print $1;}' | tr '\n' ',' | sed 's/\(.*\)./\1/'` seeds_to_start=`echo "$torrentStatus" | grep STOPPED | grep 100% | grep UNDER | sort -k 4,4 | tail -n $((count_seed_to_start)) | \ awk '{print $1;}' | tr '\n' ',' | sed 's/\(.*\)./\1/'` #check length and assign delimeter if [ ${#downloads_to_start} -gt 0 -a ${#seeds_to_start} -gt 0 ] then delim_to_start="," else delim_to_start="" fi ids_to_start="$downloads_to_start$delim_to_start$seeds_to_start" echo "Torrent IDs to Start: $ids_to_start" ids_to_remove_one_per_line=`echo "$torrentStatus" | grep -e 'STOPPED' -e 'SEED' | grep 100% | grep OVER | \ awk '{print $1;}'` ids_to_remove=`echo "$torrentStatus" | grep -e 'STOPPED' -e 'SEED' | grep 100% | grep OVER | \ awk '{print $1;}' | tr '\n' ',' | sed 's/\(.*\)./\1/'` echo "Torrent IDs to Remove: $ids_to_remove" #Execute Actions if [ ${#ids_to_stop} -gt 0 ]; then myecho "Stopping torrents: $ids_to_stop" $REMOTE -n $REMOTE_LOGIN:$REMOTE_PASS -t $ids_to_stop --stop fi if [ ${#ids_to_start} -gt 0 ]; then myecho "Starting torrents: $ids_to_start" $REMOTE -n $REMOTE_LOGIN:$REMOTE_PASS -t $ids_to_start --start fi if [ ${#ids_to_remove} -gt 0 -a ${MOVE_AFTER_COMPLETE} -eq 1 ]; then myecho "Moving torrents: $ids_to_remove" $REMOTE -n $REMOTE_LOGIN:$REMOTE_PASS -t $ids_to_remove --move "$COMPLETED_DATA_FOLDER" echo "Removing torrents that are in Completed folder..." for i in $ids_to_remove_one_per_line; do this_torrent_data_location=`$REMOTE -n $REMOTE_LOGIN:$REMOTE_PASS -t $i -i | awk '/Location/'|sed -e 's/ Location: //'` echo "Location of torrent $i is: $this_torrent_data_location" if [ "$this_torrent_data_location" = "$COMPLETED_DATA_FOLDER" ]; then myecho "Removing Torrent $i from the list..." $REMOTE -n $REMOTE_LOGIN:$REMOTE_PASS -t $i --remove fi done fi } case "$rc" in start) start ;; stop) stop ;; restart) stop start ;; startup) if [ "$2" = "on" ]; then startup_on elif [ "$2" = "off" ]; then startup_off else startup fi ;; edit) edit ;; status) status ;; watch) watch ;; queue) watch queue ;; install) install ;; uninstall) uninstall ;; *) echo ${USAGETEXT} ;; esac finish_time=$(date +%s) echo "Execution Time: $((finish_time - start_time)) secs." exit 0

My Weblog post