Hi. Just for the sake of contributing some more information on this case, I went through your steps and here's what I got (also, Ubuntu 9.10 with rtorren t 0.8.2-0ubuntu2).
Case 1: 1. Add torrent (adds into a CLOSED state, so no files are created in the default directory) 2. Change torrent download directory 3. Start the download (files created in the new directory) 4. Kill rtorrent *not* graciously (e.g. killall -9 rtorrent) to simulate a crash 5. Start rtorrent Result: rtorrent opens with the torrent in the CLOSED state and directory set to the *default* directory. (5a - no effect). Start rtorrent (files created in default directory, since nothing was ever there), stop and close the torrent back. 6. Change download directory to the new directory (with partial data) 7. Start the torrent (Ctrl-s) Result: Hash re-check is automatically triggered and torrent download is continued into the new directory. At least this use case does not necessary suggest a bug. rtorrent is not cleanly shut down so the directory change does not make it to the session file, so when it starts back up the session information is out- of-date. The straightforward recovery from the situation worked for me (whereas it did not for you -- strange). I haven't read the code, so this might not be relevant, but perhaps session changes could be pushed to the file more frequently (and maybe fsync() should be used, esp. on events like directory change) -- just a thought. Note that if I cleanly quit rtorrent in step 4, then the directory change is remembered as expected. By the way, to change the default directory without reloading .rtorrent.rc you can do Ctrl-x, directory=/path/to/dir. Case 2: 1. Add torrent 2. Start torrent (creates files in the default directory) 3. Stop and close torrent 4. Change directory 5. Try to start torrent (Ctrl-s) Result: Cannot start torrent (error in log: "could not find file [one of torrent content files in torrent's new directory]"). 6. Try initiating hash recheck (Ctrl-r). Result: rtorrent *crashes* with "rtorrent: TrackerManager::send_later() m_control->set() == DownloadInfo::STOPPED." and return code 255. This use case looks like a bug, though. But maybe it was fixed in latest version of rtorrent.. I should try that soon. -- directory change not saved https://bugs.launchpad.net/bugs/502653 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
