Transmission

[My post crossed with yours, so thanks for the reply.]

<torrentid> is an integer (a real ID) referring to the torrent I want to remove.

I have no idea why this fixed the problem, but it did:

sh -c "transmission-remote -n <username>:<password> -t <torrentid> --remove"

I have a (bash) script that periodically looks for completed torrents that are above a certain ratio. When it finds a match, the script deletes the torrent.

The line is:

transmission-remote -n <username>:<password> -t <torrentid> --remove

(I have also tried -r in place of --remove.)

Whatever I ...

[Ubuntu 18.04.3]

I'm getting the following non-fatal warnings when I start up transmission:
UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)

so I've added the following lines to /etc/sysctl ...

I am deleting torrents as part of a shell script with the following line:

/usr/local/Cellar/transmission/2.94/bin/transmission-remote -n admin:admin -t $REF -r | tr -d "\n");
($REF is the torrent id to be deleted and I am piping to tr to strip the newline character.)

I test whether this works ...

Is there any way to identify a stalled torrent through the CLI:

transmission-remote -l

other than to look at each torrent with:

transmission-remote -t <torrent> -i

for its latest activity?

I assume that the (Mac) client must be calculating the time between now and latest activity to enable ...