Auto-Tools help

[das329717]

I have all of the autotools enabled and configured but it is not picking up any of the torrent files I have.

I believe I am using php cli. Here is the output of 'php -v'
Code:
PHP 5.2.12 (cli) (built: Jan 1 2010 11:17:49)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies

This is the autotools log
Code:
12.05.10 15:15:26] AutoWatch: --- begin ---
[12.05.10 15:15:26] AutoWatch: enabled : 1
[12.05.10 15:15:26] AutoWatch: autostart : 1
[12.05.10 15:15:26] AutoWatch: path_to_watch : /volume1/Warehouse/Incoming/Torrents/
[12.05.10 15:15:26] AutoWatch: get_directory : ./

In my php.ini I have 'register_argc_argv = On'

If I set rtorrent's watch dir on it picks up torrents in the Incoming/Torrents directory right away. But when I disable it and enable autotools it does not find any of the torrents in the subdirectories Incoming/Torrents/Music, Incoming/Torrents/Movies, etc.

Sorry for cross posting this. I just saw this sub-forum.

 

[shwetha17]

looks like auto-watch is working.


Which part of auto-tools doesn't work?

 

[somus1735]

The torrents are never actually load and start downloading.

 

[jith45]

• hrm....that's strange.
  
  The guy who wrote this plugin hasn't been around much....i'd try to open a ticket on the main googlecode page and hopefully he will see it.

 

[dsouvik215]

Somewhat of an old topic, but I ran into this problem on a new setup and thought I would post. It looks like there is a path problem in autotools somewhere. If you use ./ or something relative in the downloads folder setting (general/download, here its listed as the get_directory) then autotools resolves it relative to itself, not rutorrents root. This seems to be fouling things up, when I put a full path in the downloads directory instead of relative it seems to work fine.

Also I noticed changing the downloads directory doesn't seem to notify autotools that it has changed, and until you refresh the webpage it will continue to attempt to use the old path. I need to confirm this before submitting an issue though, might have just been me

 

[shwetha17]

no, it's a real issue. The problem is the guy who wrote the plugin doesn't seem to be adding to it or fixing bugs