host busy flag in freezer

[Timuckl]

Hi again!

I continued working on the manager got the every to work even with the
older sql dump.

I have one strange effect ...
When the Burner starts the process the Burner slave ui status is
"Busy", but in the freezer it is still set to "ready".
The job name is written into current job, but the status is always
"ready".

Am I missing a script that updates that or is it normal?

Thanks in advance
Timo

[Barry Robison]

Ok, I am back from holiday vacation now, sorry for the delay.

So this is basically a legacy from when Arsenal went from single job per host to the current "multi-slot" architecture. Now a host is never at status "busy". Some or all of its slots may be taken, but the host is still "ready" to receive commands.

I'd have to review the slave logic, but I think if it has any active assignments it says "Busy" so a workstation user can kill it if they want to work.

hth,
-barry