Perfect, that made it work properly again - thanks

I've been using Deluge 1.3.x for some time, as a local thin client & remote server running on a seedbox. Today I upgraded to 2.0.3. While everything is running well, the thin client now re-shows the password prompt each & every time I launch (aka it doesn't seem to remember the password as i...

Well that was a nightmare. You forgot a *critical* switch: you need to specify the --fork parameter to deluge-web, otherwise it won't terminate, nor will the start script, and thus, the device will lock up and not finish booting. I was only able to fix this by pulling the drive, hooking it up to ano...

I've done these things to run deluge at boot: 1) vi /usr/syno/etc/rc.d/S92delugeweb.sh 2) paste this script case $1 in start) chroot /volume1/ debianchrootdir / su - yourusername -c "/usr/bin/deluged" chroot /volume1/ debianchrootdir / su - yourusername -c "/usr/bin/deluge-web" ...

Already is that way. The startup script I'm using is this one: http://dev.deluge-torrent.org/wiki/UserGuide/InitScript/Ubuntu, which I have running as root - and /var/log/deluge is owned by root. That's what u mean, right? So u actually do have it starting up automatically on reboot? If so, mind sha...

I've already done that. Please see my very first post in this thread.

You mean make a script that calls the start script, rather than just calling the start script? Why would that make a difference? I'm really not a linux person, but to put that in Windows terms - calling a batch file, or calling a batch file that calls a batch file...sounds like the same result to me...

Regarding your latter issue, I've had no such problems myself - but if you're wanting to bring up some unrelated issue, please create its own thread rather than change the subject of this one. I'm still hoping someone can come around and figure out how to fix the topic of *this* thread: "Gettin...

Based on the fact that I can stop/start it manually from the Debian Chroot console, it seems unlikely that it'd be permissions (right?) - so it's probably an issue of another service not having started. How would one approach debugging that, and/or forcing the Deluge service to start later...?

Yup...if you do, it'd be much appreciated! I seriously spent like a whole day googling around for ideas, nothing worked though...