Rsync with ssh proxy how to#

The SUP client performs all the steps needed to execute commands through the SUP as if the SUP itself did not exist. Your_localhost% sup scp foobar pfe 21:/nobackupp2/ username/c_ foobar Authorize directories for write operations (one or more times per host):.Authorize host for SUP operations (one time per host):.Download and install the SUP client in your personal bin directory (one time).In these steps, host refers to a PFE or LFE the command lines shown are examples. Each step is explained in more detail in subsequent sections.

Rsync with ssh proxy how to#

The steps in this section demonstrate how to quickly get up and running with the SUP. Note: The shiftc command is built into the sup command therefore, when you download the SUP client, you will also get shiftc.

In the future, other operations may be available via the SUP. SUP keys are currently allowed to call scp, sftp, qstat, rsync, shiftc, ssh-balance, and test. To accomplish this, you must first obtain special 'SUP keys' using RSA SecurID authentication, which you can then use to perform operations from unattended jobs and/or scripts. Each SUP key is valid for a period of one week from the time it is generated. You may have multiple SUP keys at the same time, which will expire asynchronously. The Secure Unattended Proxy ( SUP) allows you to perform remote operations on specific hosts within the NAS enclave (currently, the Pleiades and Lou front-end systems ) without needing to use your RSA SecurID token at the time of the operation.