This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
archive:bioinformatic_tools:udt [2010/06/30 18:14] jstjohn |
archive:bioinformatic_tools:udt [2015/07/28 06:27] (current) ceisenhart ↷ Page moved from bioinformatic_tools:udt to archive:bioinformatic_tools:udt |
||
---|---|---|---|
Line 23: | Line 23: | ||
recvfile [send_ip_address] [send_port_num] [full/path/to/file/on/send/machine] [./recieve_file_name] | recvfile [send_ip_address] [send_port_num] [full/path/to/file/on/send/machine] [./recieve_file_name] | ||
| | ||
- | Note that this will transfer the single file, then close the sendfile connection on the sending machine once the transfer is complete. Since you can't easily write a script to iterate through a bunch of files and/or folders due to this problem where you have to execute sendfile on one end and recvfile on the other end at the right time, the best option would probably be to archive all files you want to transfer at one time into a single .tar file and then transfer that file. To create a tarball of a directory (without any compression) execute this command: | + | Note that this will transfer the single file, then close the sendfile connection on the sending machine once the transfer is complete. Unfortunately I have not been able to figure out how to get it working on folders. Since you can't easily write a script to iterate through a bunch of files, the best option would probably be to archive all files you want to transfer at one time into a single .tar file and then transfer that file. To create a tarball of a directory (without any compression) execute this command: |
tar cvf output.tar input_folder/ #creates a tar archive of the folder and its contents | tar cvf output.tar input_folder/ #creates a tar archive of the folder and its contents |