More than one demon simultaneously

[Noko]

Is there a way to run few demons simultaneously, and have few clients connect, each one to own demon, so their settings and downloads are not shared? I tried running them with different port and config dir, and everything works like a charm until I kill demons. Next time I launch them (with same parameters), they all have same settings and are downloading same torrents.

[Menpachi Hibachi]

Use the -c option to specify a different configuration directory for each daemon when you start them.

[Noko]

Yeah, well, that's what I am doing:

Code: Select all

$ cp -r ~/.config/deluge ~/1.cfg
$ cp -r ~/.config/deluge ~/2.cfg
$ deluged -p 1025 -c ~/1.cfg
$ deluged -p 1026 -c ~/2.cfg
$ deluge

<connecting to :1025, going to settings window, setting download directory to ~/1; connecting to :1026, going to settings window, setting download directory to ~/2;>

$ killall deluged
$ deluged -p 1026 -c ~/2.cfg
$ deluged -p 1025 -c ~/1.cfg
$ deluge

<connecting to :1025, download directory is set to ~/1; connecting to :1026, download directory is set to ~/1; (while it should be ~/2)>

[andar]

Yeah, well, that's what I am doing:

Code: Select all

$ cp -r ~/.config/deluge ~/1.cfg
$ cp -r ~/.config/deluge ~/2.cfg
$ deluged -p 1025 -c ~/1.cfg
$ deluged -p 1026 -c ~/2.cfg
$ deluge

<connecting to :1025, going to settings window, setting download directory to ~/1; connecting to :1026, going to settings window, setting download directory to ~/2;>

$ killall deluged
$ deluged -p 1026 -c ~/2.cfg
$ deluged -p 1025 -c ~/1.cfg
$ deluge

<connecting to :1025, download directory is set to ~/1; connecting to :1026, download directory is set to ~/1; (while it should be ~/2)>

It looks like you may be setting the config directory to a file. If this is the case, then you're going to have issues.

[Noko]

Oh, it's a directory. ~/.config/deluge is a directory, I'm copying it with -r.

[andar]

What version of deluge are you running?

[Noko]

1.1.9, from debian repositories.

[Menpachi Hibachi]

Look inside core.conf in each config directory. Some of the variables include full paths, particularly the state_location entry which defines what torrents the client is working with. Just copying them like you did is not enough.

You should also look at the torrents.state file, it specifies the path to each download. If you just copy it the way you did then any torrents that were already in process when you copied the config dir will also be in process in the new instance.