From 2f7a9777db4be98ee43289d3841e7ccca02c1121 Mon Sep 17 00:00:00 2001 From: PyroScope Project Date: Sun, 20 Aug 2017 14:55:10 +0200 Subject: [PATCH] Delayed Completion Handling --- Common-Tasks-in-rTorrent.rest | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Common-Tasks-in-rTorrent.rest b/Common-Tasks-in-rTorrent.rest index d3207c5..e6cdd68 100644 --- a/Common-Tasks-in-rTorrent.rest +++ b/Common-Tasks-in-rTorrent.rest @@ -106,6 +106,16 @@ Each watch directory adds torrents with the final destination stored in the ``cu method.set_key = event.download.finished,move_complete,"d.move_to_complete=$d.get_data_full_path=,$d.custom1=" +Delayed Completion Handling +------------ + +`Delayed Completion Handling`_ (click for details) shows how to add a new ``event.download.finished_delayed`` trigger that works like the normal finished event, but only fires after a customizable delay. + +One use-case for such a thing is to move a download from fast storage (RAM disk, SSD) to slow storage (HDD) for permanent seeding, after the initial rush in a swarm is over. + +.. _`Delayed Completion Handling`: https://rtorrent-docs.readthedocs.io/en/latest/use-cases.html#delayed-completion-handling + + Move .torrent file after loading it manually ------------