Replies: 1 comment
-
I think I figured out what was happening. I kept loading the same torrent over and over to test. I would remove it, deleting data (through ruTorrent) and one of the times, it failed to delete the folder in my done directory. So the bad return code was actually coming from the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm tying to have rtorrent execute a local python script and pass the torrent hash to it. I'm running 0.9.8/0.13.8. In .rtorrent.rc I have this:
method.set_key = event.download.finished,notify_python,"execute2={/home/user/python/bin/python,/home/user/test.py,$d.base_path=,$d.base_filename=,$d.hash=}"
When I do this, I see in the rtorrent UI a message pop up that says bad return code. My python script right now is very basic, just trying to see if it executes:
Nothing shows in the log when I see the bad return code error. If I change .rtorrent.rc and remove the
$d.hash=
item, my log prints like I expect:If I run the python script manually with the hash code copy/pasted from the UI, the script logs it out just like I expect. Is there something different with
$d.hash=
than with the other common items I have in .rtorrent.rc? Thanks!Beta Was this translation helpful? Give feedback.
All reactions