Re: [HTCondor-users] time of day policy

[John M Knoeller <johnkn@xxxxxxxxxxx>]

have a look at 

use POLICY : DESKTOP_HOURS

it does not have any notion of request_runtime however. 

-tj

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Beyer, Christoph <christoph.beyer@xxxxxxx>
Sent: Friday, June 20, 2025 6:09 AM
To: htcondor-users <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] time of day policy

 

Hi,

I have a question :)

I am looking for a smart solution to not only not start jobs in a certain time span on a host but also I do not want to start jobs earlier that come with a runtime intruding in the idle period of the machine.

I have a suspicion that the clockmin/clockday policy would be a good way to implement it but not sure. For now I inherited the example from the manual:

WorkHours = ( (ClockMin >= 480 && ClockMin < 1020) && (ClockDay > 0 && ClockDay < 6) )
AfterHours = ( (ClockMin < 480 || ClockMin >= 1020) || (ClockDay == 0 || ClockDay == 6) )
START = $(START) && $(AfterHours)
MachineBusy = $(WorkHours)

Does that automatically respect the request_runtime of the jobs because it may tinker with the uptime value of the host ?

Best
christoph

--
Christoph Beyer
DESY Hamburg
IT-Department

Notkestr. 85
Building 02b, Room 009
22607 Hamburg

phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe

Join us in June at Throughput Computing 25: https://urldefense.com/v3/__https://osg-htc.org/htc25__;!!Mak6IKo!OsAwWfvfipNc4vuoBlekWHgo7IR_sesquh3sq3Hy7fA2YNW6srViKLy90qBsfaLdN40ZyFPmXuIllj45MF9ntAZBRwco$

The archives can be found at: https://www-auth.cs.wisc.edu/lists/htcondor-users/