From e89333ed7d8d4a46a1b02b1cf3f4e45435ddd7f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Str=C3=B6nisch?= <sebastian.stroenisch@tu-dresden.de> Date: Mon, 27 Mar 2023 15:51:00 +0200 Subject: [PATCH] Add FileZilla mentioning to export_nodes.md --- doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md b/doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md index 36cfb088d..c54e0c23f 100644 --- a/doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md +++ b/doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md @@ -4,7 +4,7 @@ To copy large data to/from ZIH systems, the so-called **export nodes** should be possible to transfer small files directly via the login nodes, they are not intended to be used that way. Furthermore, longer transfers will hit the CPU time limit on the login nodes, i.e. the process get killed. The **export nodes** have a better uplink (10 GBit/s) allowing for higher bandwidth. Note -that you cannot log in via SSH to the export nodes, but only use `scp`, `rsync` or `sftp` on them. +that you cannot log in via SSH to the export nodes, but only use `scp`, `rsync` or `sftp` (incl. FTP-clients like e.g. [FileZilla](https://filezilla-project.org/)) on them. The export nodes are reachable under the hostname `taurusexport.hrsk.tu-dresden.de` (or `taurusexport3.hrsk.tu-dresden.de` and `taurusexport4.hrsk.tu-dresden.de`). -- GitLab