Hi there,
We hit an issue every once and again, where if a machine is mostly only used to submit jobs by an artist, but he doesnt really use neither the monitor, nor the slave for overnight renders, he can end up being stuck with very old versions. Can you guys think of some elegant way of auto-updating machines that have the launcher running, but neither the monitor/slave is triggered regularly? Say, once every night, do a version check kinda thing?
cheers,
laszlo
Hey Laszlo,
We could look at making the upgrade trigger automatically by having the launcher check periodically. It would be more convenient then having to send out a “restart slave” message to all your machines. The Launcher could check if the slave, monitor, or pulse is running, and then handle it accordingly. For example:
- If slave is running, upgrade after it finishes it’s current task.
- If the monitor is running, display a countdown message so that if someone is using it, they can postpone it.
- If pulse is running, trigger a housecleaning before the upgrade.
If no applications are running, then just do the upgrade immediately.
We’ll put this on the todo list. It could be a 6.1 thing if we have time.
Cheers,