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

[Michael DiDomenico <mdidomenico4@xxxxxxxxx>]

i can't say this is the best way, but how i do it is using a
CANRUNJOBS variable in the start expression.  and then twiddle the
variable using a startd cron job that runs every 10secs.  we have
various things that can stop jobs on a box but one of the twiddles is
whether the uptime is greater then 15mins

On Wed, Nov 5, 2025 at 1:58âPM Andrew Pickford <andrewp@xxxxxxxxx> 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?
>
>
> Thanks,
>
> Andrew
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
>
> The archives can be found at: https://www-auth.cs.wisc.edu/lists/htcondor-users/