Due to the limited renderfarm size I often use the workstation as a slave.
Generally I let it finish the task by using the “stop slave after task completion” command
And then disable the slave to prevent it from starting again while I’m working.
It would be nice to have a new option in the slave command window being “disable slave after task completion”
This would prevent situation where the slave starts again and tasks need to be cancelled.
I can of course disable the slave directly after the “stop slave after task completion” has been triggered.
But figured this would be cleaner.
In 6.1, we changed how a Disabled slave works so that it can continue to run (or be launched), but it simply won’t pick up any tasks. So if you disable a slave, and that slave is in the middle of rendering, it will finish its task and then won’t pick up any new ones. So functionally, it already does what you want it to do (other than actually shutting down the slave).’
Note that if a slave becomes disabled while it’s rendering, it will return its license, so it won’t count against your license usage total.
Does that mean power management will now affect disabled slaves? We used to just disable a slave to perform maintenance on it. Someone just yesterday said it didn’t work but I assumed they were doing it wrong.
The behavior for Power Management shouldn’t be any different. The Machine Startup still skips over disabled slaves, and Idle Shutdown never had any special case for disabled slaves.
The main reason to ask it is to prevent the slave in the overview staying “stuck” on it’s last job description.
Currently I disable a slave while it’s rendering (to finish it’s current task, but not take a new one).
This results in the slave displaying it’s last render task indefinitely in yellow and at 100% :
Which won’t be changed until I restart the slave again.
Which, for me sometimes works confusing (the fact that a slave is disabled but still shows info)
Yup, that was the bug. The slave wasn’t unloading its current job if was disabled while in the middle of a task, which is why the job information was still being shown. So in RC3, the slave will properly unload its job in this case after it finishes its current task.
