Hi
I’ve been setting up 6 side by side with 5.2, testing dl6 in production, and so far it’s working well.
Except it looks as though launcher 6 will take down launcher 5 and slave 5 as well when it detects it needs to auto update.
Any chance it can target the process kills? (assuming it is killing processes by name).
thanks
grant
Hey Grant,
The Launcher has a fallback if the slave applications on the machine don’t exit in a timely fashion, and that is to kill them. So this means that other versions of the slave will get taken down too (since they’re all just called ‘deadlineslave.exe’).
We would prefer not to “weaken” this fallback, so I’m not sure if we’ll be able to do anything about this.
Cheers,
Deadline6slave.exe?
We could perhaps consider that for Deadline 7. Unfortunately it’s a bit late in the beta to make this change now.
I know the nKill app I use on windows to kill processes (like, 3dsmax) allows you to specify what to kill by path: given that tool does it, can you query the path of the process, not just the name?
ie any chance the launcher can check it’s own path against the path of the processes it’s killing, that would sort it I would think.
thanks,
grant
Hey Grant,
We looked into this a bit more, and it looks like we really don’t need that final fallback. When the launcher is closing slaves, it is getting the slave listening port and pid from the Deadline6 user folder. If a slave is running that doesn’t have its information in that folder, we can simply assume it’s a different version of Deadline, and don’t need to try and kill.
I removed that fallback code and tested it, and the launcher was able to do a full Deadline 6 upgrade while all the Deadline 5 applications were running, so I think we’re good! This fix will be included in beta 16.
Cheers,
That’s great, thanks!