You are not logged in.
Hi,
I'm not sure what should I do. The wiki page says:
Deluge comes with a daemon called deluged. If it is not running when one of the clients is run, it will be started.
But I just checked, I was running deluge client, but no deluge daemon was started:
# pgrep -a deluge
1155 /usr/bin/python2 /usr/bin/deluge-gtk
Then I started deluge daemon:
# systemctl start deluged
# pgrep -a deluge
1155 /usr/bin/python2 /usr/bin/deluge-gtk
10475 /usr/bin/python2 /usr/bin/deluged -d
I'm running deluge-1.3.7-3. It may be possible, that in previous versions it worked that way? Or not? Should I have done something other than asking the forum?
Offline
No, you are correct. If I remember, there is a setting in the GUI that will auto-start the daemon, but it isn't enabled by default.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Actually, I can't find this setting.
Offline
I think it depends on the mode of operation, server vs standalone. Can't remember.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I now probably see, what you meant. There's "Classic Mode", in which it just acts as a standalone application and doesn't autostart the daemon, and doesn't probably connect to it, if it's already started. If not in Classic Mode, it just presents you with a Connection Manager, where you can start the daemon and connect to it.
Last edited by x-yuri (2014-09-14 09:17:20)
Offline
Also, in Connection Manager there are options "Automatically connect to selected host on start-up" and "Automatically start localhost if needed". So it may be made to autostart and autoconnect the daemon, but not by default.
Offline