Deluge Forum

I was doing some testing of 1.04 today on my Windows server. It works great, provided I manually start both the Daemon and the WebUI. Unfortunately, I can't set either of the available .CMD files to run on Startup, because all of the shortcuts trigger duplicate deluge.exe, deluged.exe, and python.exe processes. And unfortunately the root .exe processes don't launch on their own.

I don't know Python, but these .cmd files are batch scripts that call the Python files to run the Deluge files, correct? Would it be possible to integrate these into single .exe files instead, that potentially could check for existing instances? That way, you'd be protected from user error (accidentally triggering 20 deluged.exe instances). And, best of all, it would allow for running the Daemon/WebUI as a Windows service or Windows startup item.

Just a request-- maybe something for 1.1?

Bard09 wrote:I was doing some testing of 1.04 today on my Windows server. It works great, provided I manually start both the Daemon and the WebUI. Unfortunately, I can't set either of the available .CMD files to run on Startup, because all of the shortcuts trigger duplicate deluge.exe, deluged.exe, and python.exe processes. And unfortunately the root .exe processes don't launch on their own.

I don't know Python, but these .cmd files are batch scripts that call the Python files to run the Deluge files, correct? Would it be possible to integrate these into single .exe files instead, that potentially could check for existing instances? That way, you'd be protected from user error (accidentally triggering 20 deluged.exe instances). And, best of all, it would allow for running the Daemon/WebUI as a Windows service or Windows startup item.

Just a request-- maybe something for 1.1?

It does check for running instances.. The cmd files are necessary to setup proper PATHs for Deluge to work since we include a copy of python.

So... if I'm seeing new instances load when the shortcuts are clicked for a second time (meaning they persist running in memory) this would be a bug, correct?

Because I am seeing that. Let me know if there's anything I can do for you to debug the cause of this issue.

Bard09 wrote:So... if I'm seeing new instances load when the shortcuts are clicked for a second time (meaning they persist running in memory) this would be a bug, correct?

Because I am seeing that. Let me know if there's anything I can do for you to debug the cause of this issue.

It is possible for 2 instances to run if they are started very shortly after each other, before the global mutex is set.