On Thu, Jun 5, 2014 at 6:22 PM, Rita <rmorgan466@xxxxxxxxx> wrote:
Rita,
The configuration you proposed won't work because 'running' gets
> if a job is running on that machine I don't want it to be scheduled. i want
> only a single jobs to run on one machine.
inserted into the job ad, but the Requirements _expression_ looks at the
slot ad. You can insert job ads into the slot ad with
STARTD_JOB_EXPRS, but 1) that violates your "don't change execute
configuration" constraint and 2) only works on a per-slot basis. The
second point can be somewhat mitigated with STARTD_SLOT_ATTRS, but at
the expense of making your requirements _expression_ increasingly
cumbersome.
Your best bet is to either use partitionable slots, or the "Whole
Machine Slots" recipe at:
https://htcondor-wiki.cs.wisc.edu/index.cgi/wiki?p=WholeMachineSlots
Thanks,
BC
--
Ben Cotton
main: 888.292.5320
Cycle Computing
Leader in Utility HPC Software
http://www.cyclecomputing.com
twitter: @cyclecomputing
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/