Custom Query (2449 matches)

because of absolute paths in web ui deluge can not work through http server proxy

for example apache mod_proxy:

ProxyPass /deluge/ ​http://127.0.0.1:8112/ ProxyPassReverse /deluge/ ​http://127.0.0.1:8112/

No contents from /static received, redirect to /index also does not work because of absolute path.

I have 1500 active torrents in deluged. When I use deluge-console, it connects quickly, but the info command is very slow (it takes more than a minute with 100% CPU usage in the deluge-console process; deluged uses less than 20% CPU).

The same thing happens when establishing the connection from the GTK-UI to deluged: after clicking the *Connect* button, it takes more than a minute to see the torrents with 100% CPU usage in the deluge-console process, and deluged uses less than 20% CPU. Once connected, everything is fast.

How can I diagnose this myself? How should I start the GTK-UI so that I get some CPU profiling info?

To package deluge=1.0.0 for Foresight I needed to change setup.py to workaround a broken boost package. The changes made could help other packagers build Deluge.

Firstly /usr/lib/libboost_filesystem.so only exists when building for x86, for x86_64 it is in /usr/lib64, I suggest changing the logic to use LIBDIR rather than /usr/lib explicitly.

Secondly all the boost libraries *except* boost_thread are available as both -mt and non -mt. To workaround that I changed it explicitly in _libraries. However combined with the first problem however this failed unexpectedly building for both arches - it tried to use boost_thread-mt-mt. So I added a further check before appending -mt.