HTCondorWiki: Using Condor Annex On Chtc

 requirements = (regexp( ".*\.ec2\.internal", Machine ) || IsCHTC) && (OpSysMajorVer isnt defined || OpSysMajorVer == 6)
 {endverbatim}
 
+If you prefer, you can restrict by the name of the annex you requested (but be aware that any annex user can assign any name to their annex, including one that you're already using):
+
+{verbatim}
+requirements = (AnnexName =?= "MyFirstAnnex" || IsCHTC) && (OpSysMajorVer isnt defined || OpSysMajorVer == 6)
+{endverbatim}
+
 You can also edit existing jobs by using =condor_q=.  More on using this tool will be forthcoming.
 
 Once you've gotten one job running, you may want to add additional resources to your annex.  While repeating the command from section 3 will add another instance to the "MyFirstAnnex" annex, for simplicity we recommend using another name.  (Using an existing name updates the lease for all instances in the annex, existing and new; but only new instances will respect the new max idle time.  If you've used the name of your annex in your job requirements, this might be worth the trouble.)