Using Condor Annex On Chtc

Not logged in

• Browse
• Help
• Home
• Login
• Reports
• Search
• Timeline
• Wiki

• Contents
• No-Diff
• Text

 $ condor_qedit 100234.5 requirements '(TARGET.AnnexName == "MyFirstAnnex" || TARGET.PoolName == "CHTC") && ((Target.OpSysMajorVer =?= 6) || (Target.OpSysMajorVer =?= 7)) && (OpSysName =!= "Debian") && (TARGET.Arch == "X86_64") && (TARGET.OpSys == "LINUX") && (TARGET.Disk >= RequestDisk) && (TARGET.Memory >= RequestMemory) && (TARGET.HasFileTransfer)'
 {endterm}
 
-Execute the following commands to set =MayUseAWS= and =WantFlocking= as required.  (Note that when editing a job in the queue, these attribute names are _not_ preceded by a plus ('=+=') sign.)  A reminder: this means these jobs will flock!  For now, you shouldn't use =condor_annex= if you don't want your jobs flocking.
+Execute the following commands to set =MayUseAWS= and =WantFlocking= as required.  (Note that when editing a job in the queue, these attribute names are _not_ preceded by a plus (' =+= ') sign.)  A reminder: this means these jobs will flock!  For now, you shouldn't use =condor_annex= if you don't want your jobs flocking.
 
 {term}
 $ condor_qedit 100234.5 MayUseAWS TRUE

This work is supported by NSF under Cooperative Agreement OAC-2030508 as part of the PATh Project. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF. Site built using CVSTrac.