+
\ No newline at end of file
From 653423e8cfd64aeb181736db1a3ce8aac6b2730f Mon Sep 17 00:00:00 2001
From: JoschD <26184899+JoschD@users.noreply.github.com>
Date: Thu, 26 Jun 2025 18:39:44 +0200
Subject: [PATCH 2/2] follow symlinks
---
docs/resources/shared_filesystems.md | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/docs/resources/shared_filesystems.md b/docs/resources/shared_filesystems.md
index 3a9528c7..593037ca 100644
--- a/docs/resources/shared_filesystems.md
+++ b/docs/resources/shared_filesystems.md
@@ -25,11 +25,17 @@ mkdir ~/mnt/eos && ln -nfs ~/mnt/eos /eos
### Mount network resources (repeat after timeouts and restarts)
```bash
-sshfs username@cs-ccr-dev3.cern.ch:/user/ ~/mnt/user
-sshfs username@cs-ccr-dev3.cern.ch:/nfs/ ~/mnt/nfs
-sshfs username@lxplus.cern.ch:/eos/ ~/mnt/eos
+sshfs -o follow_symlinks username@cs-ccr-dev3.cern.ch:/user/ ~/mnt/user
+sshfs -o follow_symlinks username@cs-ccr-dev3.cern.ch:/nfs/ ~/mnt/nfs
+sshfs -o follow_symlinks username@lxplus.cern.ch:/eos/ ~/mnt/eos
```
+??? info "Follow Symlinks"
+ When mounting to a different location than `/nfs` or `/user` **locally**, one has to set the `follow_symlinks` option
+ so that symlinks e.g. pointing to a folder somewhere in `/nfs/` (which locally does not exist) are followed correctly, i.e. to the path on the remote machine.
+ This is not needed when mounting to `/nfs` or `/user` as the symlinks would point to these locations anyway,
+ but that comes with its own problems, as the mount needs to be done as **root** in these cases and might not be valid for other users.
+
### If outside of the GPN, jump through `lxplus` to mount `dev3`-folders
```bash