Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[condor-users] diff copy_to_spool transfer_executable
- Date: Tue, 27 Jan 2004 17:35:50 +0100
- From: Olivier Ricou <ricou@xxxxxxxxxxxxx>
- Subject: [condor-users] diff copy_to_spool transfer_executable
Hi,
Can someone explain me the difference between the copy_to_spool command
in the submision file and the transfer_executable command please ?
copy_to_spool = <True | False>
If copy_to_spool is set to True, then condor_ submit will copy the
executable to the local spool directory before running it on a
remote host. Oftentimes this can be quite time consuming and
unnecessary. By setting it to False, condor_ submit will skip this
step. Defaults to True.
transfer_executable = <True | False>
For jobs submitted to the globus universe, as well as vanilla and
MPI. If transfer_executable is set to False, then Condor looks for
the executable on the remote machine, and does not transfer the
executable over. This is useful if you have already pre-staged your
executable and wish to have Condor behave more like rsh. Defaults to
True.
TIA,
Olivier.
Condor Support Information:
http://www.cs.wisc.edu/condor/condor-support/
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>