Transfer from Madison: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
umask 0002 && rsync -avP --no-implied-dirs --relative MADISON_USERNAME@data.icecube.wisc.edu:/data/DIRECTORIES/FILES / && umask 0022 | umask 0002 && rsync -avP --no-implied-dirs --relative MADISON_USERNAME@data.icecube.wisc.edu:/data/DIRECTORIES/FILES / && umask 0022 | ||
* umask is used to set correct permissions for group (if not specified, other users won't be able to write in | * umask is used to set correct permissions for group (if not specified, other users won't be able to write in created directories !) | ||
* MADISON_USERNAME is optional if it is the same as the T2B one | * MADISON_USERNAME is optional if it is the same as the T2B one | ||
Revision as of 13:52, 19 January 2017
To transfer files and keep their structure identical, use the following command on m-machines :
umask 0002 && rsync -avP --no-implied-dirs --relative MADISON_USERNAME@data.icecube.wisc.edu:/data/DIRECTORIES/FILES / && umask 0022
- umask is used to set correct permissions for group (if not specified, other users won't be able to write in created directories !)
- MADISON_USERNAME is optional if it is the same as the T2B one
If you get an ssh_exchange_identification: Connection closed by remote host then connect to the t2 cluster adding the -A option, wich Enables forwarding of the authentication agent connection dixit man:
ssh -A mshort.iihe.ac.be