<%method component>Condor NFSLite Jobmanager <%method notes> [ { title => "What is the Condor NFSLite Jobmanager?", text => "This job manager is Condor using file transfer instead of using NFS. It is named NFSLite because there may be other reasons to be using NFS, but the job will be transferring necessary files rather than using the shared filesystem." }, { title => "Installing", text => "Use Pacman to install the Globus-CondorNFSLite-Setup package. This will install Condor, unless you have set some environment variables to specify a pre-existing Condor installation. More information " }, { title => "Setting Condor's job wrapper", text => "

In order for the CondorNFSLite job manager to work properly, you need to tell Condor to run all jobs with an job wrapper. This is a simple script that is run before all jobs. This paricular job wrapper makes sure that the job sets the working directory correctly. To tell Condor to use the job wrapper, set USER_JOB_WRAPPER in your Condor configuration file. For example:

USER_JOB_WRAPPER = /opt/vdt/post-install/condor_nfslite_job_wrapper.sh

You can find the job wrapper in \$VDT_LOCATION/post-install/condor_nfslite_job_wrapper.sh.

Description of USER_JOB_WRAPPER from the Condor 6.8 manual.

" }, { title => "Making jobmanager-condornfslite replace jobmanagercondor", text => "

By default, this jobmanager is named jobmanager-condornfslite, not jobmanager-condor. If you want this jobmanager to replace the standard jobmanager-condor, follow these steps:

" }, { title => "Tips and Tricks", text => " You might want to limit Condor jobs to only run on a subset of nodes in your Condor pool. You can edit condor.pm to change the default Requirements for a job. For example, if the jobs can run on nodes with a particular FileSystemDomain, you can set that in the requirements with (FileSystemDomain = \\\"osg.example.com\\\"). " }, ]