Transferring Files: Difference between revisions
No edit summary |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==File Transfer== | |||
Files can be transferred to and from the cluster using a client that supports the SFTP (SSH File Transfer Protocol) or with scp (Secure Copy Protocol). Free SSH or SFTP clients are available from https://www.putty.org for Windows, and are included with or available for MacOS, and most varieties of Linux/UNIX. Be sure your client is using port 22 on the login node to connect. This should be the default for most terminal and file transfer applications, but has proven to be a problem for some users unaware of the port number. | |||
Popular file transfer clients are WinSCP and FileZilla. You can download WinSCP from http://winscp.net and FileZilla from http://filezilla-project.org. Even the "rsync" utility on a Linux or WSL machine can be used with the appropriate options. Contact us to learn more about the various options for file transfers. | |||
Some users have also reported success with [http://www.itefix.no/i2/cwrsync cwrsync], a prepackaged version of Cgywin and rsync on Windows. There are numerous other SSH and SFTP clients available, and all of them should work with the login nodes. | |||
== | ==Text File Compatibility== | ||
Note that text files created under Windows may cause subtle issues. This is because Windows, MacOS, and Linux have different conventions for representing a [http://en.wikipedia.org/wiki/Newline newline] in ASCII text files. Some Windows text editors will allow you to save a file in the UNIX/Mac/Linux format before transferring the file to the cluster. Alternatively, you can use the Linux command dos2unix to remove the CR characters that Windows uses at the ends of lines, or the reverse utility unix2dos: | |||
Note that text files created under Windows may cause | |||
dos2unix somefile | dos2unix somefile | ||
| Line 14: | Line 14: | ||
dos2unix will have no effect on a Linux text file, so it's safe to use on any text file. | dos2unix will have no effect on a Linux text file, so it's safe to use on any text file. | ||
==GLOBUS Connect== | |||
This is being evaluated and tested as of late 2025. | |||
Latest revision as of 01:04, December 6, 2025
File Transfer
Files can be transferred to and from the cluster using a client that supports the SFTP (SSH File Transfer Protocol) or with scp (Secure Copy Protocol). Free SSH or SFTP clients are available from https://www.putty.org for Windows, and are included with or available for MacOS, and most varieties of Linux/UNIX. Be sure your client is using port 22 on the login node to connect. This should be the default for most terminal and file transfer applications, but has proven to be a problem for some users unaware of the port number.
Popular file transfer clients are WinSCP and FileZilla. You can download WinSCP from http://winscp.net and FileZilla from http://filezilla-project.org. Even the "rsync" utility on a Linux or WSL machine can be used with the appropriate options. Contact us to learn more about the various options for file transfers.
Some users have also reported success with cwrsync, a prepackaged version of Cgywin and rsync on Windows. There are numerous other SSH and SFTP clients available, and all of them should work with the login nodes.
Text File Compatibility
Note that text files created under Windows may cause subtle issues. This is because Windows, MacOS, and Linux have different conventions for representing a newline in ASCII text files. Some Windows text editors will allow you to save a file in the UNIX/Mac/Linux format before transferring the file to the cluster. Alternatively, you can use the Linux command dos2unix to remove the CR characters that Windows uses at the ends of lines, or the reverse utility unix2dos:
dos2unix somefile
dos2unix will have no effect on a Linux text file, so it's safe to use on any text file.
GLOBUS Connect
This is being evaluated and tested as of late 2025.