--fork tells the daemon to run in the background.

What you were doing was opening a terminal, running the daemon, killing the terminal session you were running the daemon in.

If you're using wheezy, then read this: http://dev.deluge-torrent.org/wiki/Inst ... ian/Wheezy - it walks you through adding the repository, updating the software to 1.3.6

If that works for you then do that.

I have to say though: every time I have switched to Transmission in the past I have regretted it.

I think you'd need to run deluged as a different user with a different config file and on different ports. If your startup script looks something like this: :/etc/init$ cat deluged.conf start on (filesystem and networking) or runlevel [2345] stop on runlevel [016] env uid={username} env gid={groupna...

I don't know enough about raspbian to advise you on that.

Basically, you want more up to date repositories if 1.3.3 is all they offer you in your local apt-get install.

Otherwise you are compiling your own from source via git.

Is there a reason you're not running 1.3.6 on the server?

Are you running a firewall? UPNP? Check the ports that you're using when it's not connecting, see if they change when you restart deluged. That might explain it.

Cas wrote:1.3.6 is now live on the Deluge PPA

Yay!

Thanks

Will there be a Precise lt16?

What version of libtorrent are you using?

We saw some problems back in April with people running Deluge1.3.4 with libtorrent-rasterbar0.16 - downgrading to ltr 0.15.10 fixed it for them.

One way to find out ...

What version of boost are you running? I just found that after updating a bunch of stuff I couldn't get deluged to start at all, chucked up some boost error. I have a bad feeling about boost-1.48 and v2 filesystem support, as required by libtorrent-rasterbar-15. Didn't they promise last year to remo...