Queue Manager appears to be working but isn't.

[Tom W]

Hey all,

I just discovered pyroscope while searching for a way to manage my rtorrent download queue - to limit the concurrent downloads to 5 at a time.

I'm running mythbuntu 12.04 x64 with rtorrent 0.9.3/0.13.3, rutorrent 3.5 and pyroscope installed using the install from source instructions here http://code.google.com/p/pyroscope/wiki/InstallFromSource I have installed to a different directory (~/.pyroscope) and have added /home/prime/.pyroscope/bin to the user path.

When running pyrotorque --fg -v there are no errors and it seems as though everything is working:
http://paste.ubuntu.com/6104317/

~/.rtorrent.rc
http://paste.ubuntu.com/6104321/

~/.pyroscope/config.ini
http://paste.ubuntu.com/6104324/

~/pyroscope/torque.ini
http://paste.ubuntu.com/6104327/

The problem is that the download queue in rtorrent is not limited to 5 concurrent downloads while pyrotorque is running. It seems as though pyrotorque has no control over rtorrent, but can see what is happening within rtorrent. The ~/.pyroscope/log/ directory is empty and I'm not sure where else to look for more info.

Any suggestions? Any help is greatly appreciated.

[Tom W]

Oh and I should add that commands using rtcontrol work as expected, eg:

 rtcontrol -q -s alias,message -o alias,message 'message=?*' message=\!*Tried?all?trackers* | uniq -c
      1 publicbt.com    Tracker: [Could not resolve hostname.]
      1 publicbt.com    Tracker: [Unable to connect to UDP tracker.]

[pyroscope]

# Set "pyro.bin_dir" to the "bin" directory where you installed the pyrocore tools!
# Make sure you end it with a "/"; if this is left empty, then the shell's path is searched.
method.insert = /home/prime/.pyroscope/bin/, string|const, 

This is wrong, not sure what problems it causes. Set the _value_, instead of replacing the _name_.

The problem is that the download queue in rtorrent is not limited to 5 concurrent downloads while pyrotorque is running. It seems as though pyrotorque has no control over rtorrent, but can see what is happening within rtorrent. The ~/.pyroscope/log/ directory is empty and I'm not sure where else to look for more info.

The queue works for loading torrents in STOPPED state, and control their start time. If you do not do that, it won't work (wrong expectations). The scheduler never STOPs anything by itself, giving you full manual control.

Handling these things on IRC is quite more efficient, btw. Also, there are recent fixes for the queue in SVN.