*: condor_startd *: condor_schedd -When you are done with your personal HTCondor, you can kill it with: +{subsection: Running a Simple Job} +To start a job we must first create a submit file: +{code} +> vim /scratch/local/condor84/sleep.sub +{endcode} +Once in the editor enter the following code: +{code} +# The executable variable specifies the program to be run. In this case we will call the "sleep" function +executable = /bin/sleep +# Use the following variable to pass arguments to the executable +arguments = 10 +# Use the following to specify how many of this job to queue and run +queue 2 +{endcode} +After saving your changes, it's now time to submit your job: +{code} +> condor_submit /scratch/local/condor84/sleep.sub +{endcode} +To check the status of your jobs use: +{code} +> condor_q +{endcode} + +{subsection: Closing Condor} + +If all is well with your personal HTCondor and all jobs have completed successfully, you can kill it with: {code} condor_off -master {endcode} -Remember you must use /scratch/condor84/condor.sh or some other method to set the PATH, CONDOR_CONFIG and other environment variables _before you start HTCondor or use an of the tools_. +Remember you must use /scratch/condor84/condor.sh or some other method to set the PATH, CONDOR_CONFIG and other environment variables _before you start HTCondor or use any of the tools_. {wiki: CreatingPersonalHtcondorTheHardWay A more complicated recipe that doesn't use condor_install}