simonbcn wrote:

andar wrote:The new libtorrent 0.15 version improves on how it handles these types of situations and the defaults should work better.

And what version of Deluge will use this new version of libtorrent?

You can use it with 1.2 or the upcoming 1.3.

Deluge 1.2.1 Ubuntu 9.04 32 bits What's the meaning of this error in my deluged.log? [DEBUG] alertmanager:115 performance_alert: Trainspotting_JMBD: performance warning: max outstanding disk writes reached It basically means what it says. libtorrent tries to be nice and throttles it's writes to dis...

We're working on getting this setup in git. We use to use something called a svn external to include libtorrent and the move to git has changed that.

For now, you can simply checkout the desired libtorrent branch to libtorrent/ in the deluge directory and it should build it.

simonbcn wrote:Thanks for the answer!
But I have curiosity: what are these hostlist.conf and web_plugin.conf files?

hostlist.conf is used in the connection manager to list your daemons.

web_plugin.conf i think is a legacy config file probably just being looked for to convert to a new format.

WattoDaToydarian wrote:I upgraded to 1.2.1 and the tracker still says "waffles.fm: Error: Deluge is no longer allowed or not yet approved".
Has it even been fixed yet?

Ask your tracker admins.

I suggest using 1.2.1

These warnings are benign.. It usually means you have a fresh config or are upgrading from a previous version.

In anycase, these are nothing to worry about.

Hello I would just like to confirm this problem on both an Arch Linux and a Gentoo system (deluge runs in daemon mode on the Gentoo box). Running strace on the gui's pid shows me something like endless polling. I can probably get a more accurate trace if required. I hope this gets fixed soon. Thank...

You either need to include asio or use a boost version that has it included (1.36+)

Any news on binding the bittorrent traffic to one interface (I assume the fix posted above relates only to the webserver)? I'd really like to see this feature in the client, ATM only Vuze and rtorrent do support binding the torrent traffic to one distinct interface. Thanks! This is available in 1.2