Transmission

Why do this in a separate script that has to be cronned or run manually?

Take a look at Unrar and cleanup script and change it to remove the torrent only.

Take a look at Unrar and cleanup script and change it to stop the torrent.

Mondscheinchen wrote:you could run a cronjob to restart them

Maybe it could be just as simple to run this every X minutes/hours?

transmission-remote -n $USERNAME:$PASSWORD -s

Yes it is possible to exit transmission when all the downloads are complete. Take a good hard look at the options for transmission remote. Here are some examples for Debian. You may want to change it for mac use. This yields the number of torrents that are not done: transmission-remote -n $USERNAME:...

You might want to refactor your regexps and use some meaningful names for them.

I guess that a lot of conditions / test could be lumped into a smaller number of variables.

Have you searched for a simple case conversion routine?
For example:
sed 's/\(.*\)/\L\1/'
sed 's/\(.*\)/\U\1/'

Have you tried running the script manually first? Some shells are fussy about the starting line. Have you tried this? Unrar and cleanup script As a bonus: Transmissions settings.json can not be configured while running. If you make the changes to settings.json and then stop transmission your changes...

I have updated the start post with a new script.

The only change I made was to check if unrar exits with an error code and handle it by exiting.

There are some weird rare occasions that tm thinks it's all done but the content actually is not complete or has minor corruption.

The basic queue-system found in most other clients work with a first come first serve algorithm. While this works reasonably well in general, it does not aim for (actually might harm) the goal you really want: maximum throughput! Example: Your maximum active torrent count is 4. You have 20 torrents ...

So, how is it best to prevent downloading duplicate files which I already have in my library? My idea would be to have an indexing utility that would create a hash table for all my existing files. Then when I add a torrent, the hash for each file within the torrent would be compared to the list of ...

If i have torrents that I would like not to be deleted from transmission after extraction, could you alter the script to check if the torrent has already been extracted? It looks for a file named "exit" and if it exists the script will exit. It looks for a file named "keep" and ...

One big problem with your train of thought is that the NEW torrent, containing the .srt, has nothing to do with the OLD torrent. They will have different hashes. So your example is kind of useless. However, the uploading of a specifically formatted archive might be an idea for initial seeding. Thoug...

Thank you both for your replies. I will update to 2.2x soon. For fixing this right now, do you mean my config entry should look like this: "script-torrent-done-filename": "{ /srv/transmission-emails/libevent-mail.sh >> /srv/transmission-emails/output.log 2>&1} &", Correc...

You can solve this NOW by surrounding your script with { } &.

For example: viewtopic.php?f=1&t=10364

This sounds like RPC's "torrent id" field. It is most definitely NOT. As far as I know, $TR_TORRENT_ID or the parameter for rpc just hold a simple integer index. That in itself may be error prone. The ultimate goal is that you do not have to use a username/password to manipulate a single(...

I would like to use token authentication from within the torrent-done-script. A token would only be associated with a specific torrent. It could be generated from the torrenthash + timestamp. The lifespan of a token is limited by the instantiation of the daemon, the lifetime of the torrent in transm...