From: HTCondor-users [mailto:htcondor-users-
bounces@xxxxxxxxxxx] On Behalf Of Jon Bernard
Sent: Friday, June 30, 2017 3:43 PM
Assuming you're using partitionable slots and avoiding preemption, one approach I hit upon lately is to set a unique accounting_group for the job, and then have a requirement that the ChildAccountingGroup attribute of the machine does not have that accounting group in it. This prevents it from matching with the partitionable slot if any of the dynamic slots have a copy of that job running on the machine.
> Hi all,
> We have a user who would like to ensure that he never has more than one job running per host. Is there a standard (any?) way of doing this? I've tried playing with the recipe at https://htcondor-wiki.cs.wisc.
edu/index.cgi/wiki?p=, but haven't been successful. We're using 8.5.8. HowToAllowOnlyOneUser
Â Â Â Â -Michael Pelletier.
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@cs.
You can also unsubscribe by visiting
The archives can be found at: