Angel:I'm glad the problem was straightforward. This reminds me to double check the manual where we try to list those knobs which require restart versus those that just need reconfigs.
-greg On 3/9/24 2:34 PM, Angel de Vicente wrote:
Hello,OK, so SUSPEND is defined in terms of the macro CpuBusyTimer, which is defined in terms of CpuBusyValue, and CpuBusyTime, but none are defined ,---- | $ condor_status -l xxxx.xxx | grep -i cpubusytimer `----never mind, I think the problem was that I just issued "condor_reconfig" instead of restarting Condor. After a restart (and with "use policy:desktop" in the configuration file), the machine advertises "CpuBusy", "CpuBusyValue" and "CpuBusyTime", so it is all good now. Cheers,