On 2/19/2015 2:59 PM, Dimitri Maziuk wrote:
On 02/19/2015 02:54 PM, Greg Thain wrote:On 02/19/2015 02:51 PM, Dimitri Maziuk wrote:Sorry, this doesn't make sense if I need to call it "<Keyword>_HOOK_<KIND>" and have "+HookKeyword <Keyword>" to link the job to the hook. Or is that part of the manual wrong too?The startd doesn't advertise which hooks it has (perhaps it should). So, if you know that all your startds have the hook in question, you don't need any particular requirements in your job ad, though that's not a good practice.*My* startds have the hook in question. I also have FLOCK_TO in my config.
So if your job requires some capability from the execute machine, e.g. it requires that some job hook be configured, then your job should explicitly state that in the job ad requirements expression. Then in your setup, for instance, your jobs would only be matched to "your" startds and would not be matched to startds are remote sites where you are flocking.
regards Todd
_______________________________________________ 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/
-- Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison Center for High Throughput Computing Department of Computer Sciences HTCondor Technical Lead 1210 W. Dayton St. Rm #4257 Phone: (608) 263-7132 Madison, WI 53706-1685