HTCondorWiki: Using Condor Annex On Chtc

 {section: 4 Run Jobs on Those Resources}
 
 It might take a while for =submit-4.chtc.wisc.edu= to try the other possibilities before giving the annex a chance to run the job.  Run condor_q in the terminal logged in to that machine to keep track of the test job; it should eventually run.  (Check its log
-if it's gone when you checked; the job may have run and finished.)
+if it's gone when you check; the job may have run and finished.)
 
 You can make use of the annex resources for your own jobs in two ways: by submitting new jobs and by editing existing ones.
 
-To submit new jobs, you can follow the example of the test job, above; you'll need the '+MayUseAWS = TRUE' line and the '+WantFlocking = TRUE' line.  A reminder: this means these jobs will flock!  For now, you shouldn't use =condor_annex= if you don't want your jobs flocking.  (Your job, like the test job, can require that it be run on a machine whose name ends in '.ec2.internal', but that's not a secure solution.)  You may also add 'regexp( ".*\.ec2\.internal", Machine )' to your requirements expression if you want to make sure a job doesn't run anywhere but on your annex.  You will also need to something to your requirements to address the issue that annex resources don't presently advertise =OpSysMajorVer=.  A requirements expression like the following should do the trick, where the '7' at the end is whatever version you actually need.
+To submit new jobs, you can follow the example of the test job, above; you'll need the '+MayUseAWS = TRUE' line and the '+WantFlocking = TRUE' line.  A reminder: this means these jobs will flock!  For now, you shouldn't use =condor_annex= if you don't want your jobs flocking.  (Your job, like the test job, can require that it be run on a machine whose name ends in '.ec2.internal', but that's not a secure solution.)  You may also add 'regexp( ".*\.ec2\.internal", Machine )' to your requirements expression if you want to make sure a job doesn't run anywhere but on your annex.  You will also need to something to your requirements to address the issue that annex resources don't presently advertise =OpSysMajorVer=.  A requirements expression like the following should do the trick, where the '6' at the end is whatever version you actually need.  By default, the resources =condor_annex= adds to your pool are EL6(-ish).
 
 {verbatim}
-requirements = (regexp( ".*\.ec2\.internal", Machine ) || IsCHTC) && (OpSysMajorVer isnt defined || OpSysMajorVer == 7)
+requirements = (regexp( ".*\.ec2\.internal", Machine ) || IsCHTC) && (OpSysMajorVer isnt defined || OpSysMajorVer == 6)
 {endverbatime}
 
 You can also edit existing jobs by using =condor_q=.  More on using this tool will be forthcoming.