From 3c3c8889b17fd9c2aeda693336c28c0ede579a11 Mon Sep 17 00:00:00 2001 From: Arvid Norberg Date: Wed, 7 Jan 2009 02:32:08 +0000 Subject: [PATCH] clarified how completed torrent should be treated wrt saving their resume data. Fixes #457 --- docs/manual.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/manual.rst b/docs/manual.rst index 99b7ef113..8b4517bfa 100644 --- a/docs/manual.rst +++ b/docs/manual.rst @@ -2351,7 +2351,8 @@ the `save_resume_data_alert`_ though. There's no need to pause when saving inter .. note:: It is typically a good idea to save resume data whenever a torrent is completed or paused. In those cases you don't need to pause the torrent or the session, since the torrent will do no more writing to its files. If you save resume data for torrents when they are paused, you can accelerate the - shutdown process by not saving resume data again for paused torrents. + shutdown process by not saving resume data again for paused torrents. Completed torrents should + have their resume data saved when they complete and on exit, since their statistics might be updated. In full allocation mode the reume data is never invalidated by subsequent writes to the files, since pieces won't move around. This means that you don't need to