cc_staff
1,857
edits
Transferring data: Difference between revisions
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 83: | Line 83: | ||
where REMOTENAME can be a directory or file preceded by its path location and somedir will be created if it doesn't already exist. In its simplest incarnation rsync can also be used locally within a single system to transfer a directory or file (from home or scratch) into project by dropping the cluster name: | where REMOTENAME can be a directory or file preceded by its path location and somedir will be created if it doesn't already exist. In its simplest incarnation rsync can also be used locally within a single system to transfer a directory or file (from home or scratch) into project by dropping the cluster name: | ||
{{Command|rsync -avh --no-g --no-p LOCALNAME ~/projects/def-professor/someuser/somedir/}} | {{Command|rsync -avh --no-g --no-p LOCALNAME ~/projects/def-professor/someuser/somedir/}} | ||
where somedir will be created if it doesn't already exist before copying LOCALNAME into it. | where somedir will be created if it doesn't already exist before copying LOCALNAME into it. For comparison purposes, the copy command can similarely be used to transfer LOCALNAME from home to project by doing: | ||
{{Command|cp -rv --preserve{{=}}"mode,timestamps" LOCALNAME ~/projects/def-professor/someuser/somedir/}} | |||
however unlike rsync, if LOCALNAME is a directory, it will be renamed to somedir if somedir does not exist. | |||
===Using checksums to check if files match=== <!--T:13--> | ===Using checksums to check if files match=== <!--T:13--> | ||