Administering Platform LSF - SAS

File Transfer Mechanism (lsrcp)
File Transfer Mechanism (lsrcp)
Limitations to lsrcp
Workarounds
rcp on UNIX
Custom file
transfer
mechanism
The LSF remote file access mechanism (bsub -f) uses lsrcp to process the
file transfer. The lsrcp command tries to connect to RES on the submission
host to handle the file transfer.
See “Remote File Access” on page 516 for more information about using
bsub -f.
Because LSF client hosts do not run RES, jobs that are submitted from client
hosts should only specify bsub -f if rcp is allowed. You must set up the
permissions for rcp if account mapping is used.
File transfer using lscrp is not supported in the following contexts:
◆ If LSF account mapping is used; lsrcp fails when running under a different
user account
◆ LSF client hosts do not run RES, so lsrcp cannot contact RES on the
submission host
See “User Account Mapping” on page 503 for more information.
In these situations, use the following workarounds:
If lsrcp cannot contact RES on the submission host, it attempts to use rcp to
copy the file. You must set up the /etc/hosts.equiv or HOME/.rhosts file
in order to use rcp.
See the rcp(1) and rsh(1) man pages for more information on using the rcp
command.
You can replace lsrcp with your own file transfer mechanism as long as it
supports the same syntax as lsrcp. This might be done to take advantage of
a faster interconnection network, or to overcome limitations with the existing
lsrcp. sbatchd looks for the lsrcp executable in the LSF_BINDIR directory
as specified in the lsf.conf file.
518
Administering Platform LSF