Re: [HTCondor-users] delaying job starts on execute node boot up

[Steffen Grunewald <steffen.grunewald@xxxxxxxxxx>]

On Wed, 2025-11-05 at 14:57:20 +0100, Andrew Pickford wrote:
> Hi All,
> 
> I'd like some advise on the best way to automatically stop an execute node
> from running jobs for say 5 minutes after the machine has booted up. And
> then once those 5 minutes have passed for the machine to start accepting
> jobs. The use case for this is I've drained machines and rebooted them for
> various reasons intending to do more work on them after the reboot but on
> occasion forgotten to put a START = FALSE into the nodes config and only
> realising after rebooting the machine. I could use DaemonStartTime to wait 5
> minutes after the condor daemon has started to accept jobs but I'd really
> rather the wait happen only after a reboot not on a daemon restart. Is there
> a system uptime value I've missed or any other ideas?

There's likely no "one size fits all" best way to achieve this.
You may have a "@reboot" crontab entry that adds "START = False" to the
config and runs "condor_reconfig" afterwards.
You may choose to "systemctl disable condor" and always start the service
manually.
You could have an "executable config file" that checks for the (non-)existence
of a "semaphor file", maybe somewhere on a shared filesystem.
...

Best,
 Steffen