What I understand from the error message is, that you have to set the
directory _before_ you move the files. Right?
Maybe the error message could be a little clearer. But the main problem is
the counter intuitive logic behind it (which may be required due to the
code design), and the infos in the cookbook:
Move completed torrents

When the torrent finishes, it executes "mv <base_path> ~/Download/" and
then sets the destination directory to "~/Download/". (0.8.4+)

system.method.set_key =
event.download.finished,move_complete,"execute=mv,-u,$d.get_base_path=,~/Download/;d.set_directory=~/Download/"


And by counter intuitive I mean the process of relocating something, i
believe most people do:
1. relocating from a --> b
2. tell other the relocation was successfull

But as I said, maybe rtorrent simply requires to do step 2 before 1. If I
know this, everything is fine.


2012/7/6 Jari Sundell <[email protected]>

> On Fri, Jul 6, 2012 at 5:20 AM, Max Killer <[email protected]>
> wrote:
> > Hello,
> >
> > I use rtorrent since a long time, and most of the time everything was
> great.
> > But after a recent update to the latest releases (I hoped the Looooong
> > thinking time with magnet links was gone, but it isn't), I receive a
> strange
> > error:
> >
> > * [CLOSED]  done      295.1 MB Rate:   0.0 /   0.0 KB Uploaded: 9.6 MB
> > [T  R: 0.03]
> > * Inactive: Cannot change the directory of an open download after the
> files
> > have been moved.
>
> Anyone have a suggestion for a wording of the error message that
> people will understand?
>
> Cause it stumps me trying to figure out why it isn't clear enough,
> afaics it contains everything needed for anyone to understand what
> needs fixing.
>
> Jari Sundell
> _______________________________________________
> Libtorrent-devel mailing list
> [email protected]
> http://rakshasa.no/mailman/listinfo/libtorrent-devel
>
_______________________________________________
Libtorrent-devel mailing list
[email protected]
http://rakshasa.no/mailman/listinfo/libtorrent-devel

Reply via email to