aboutsummaryrefslogtreecommitdiff
path: root/sshfs.rst
diff options
context:
space:
mode:
authorNikolaus Rath <Nikolaus@rath.org>2017-09-20 14:12:48 +0100
committerNikolaus Rath <Nikolaus@rath.org>2017-09-20 14:43:34 +0100
commit848ff30d9074371fecc332e67848375700189d05 (patch)
tree0d32f3ae94833f8921a7dde03e1aa100b8ae79e3 /sshfs.rst
parent37c8c1c80b89127d5f876a193c5fdcc916e03b6c (diff)
downloadsshfs-848ff30d9074371fecc332e67848375700189d05.tar
sshfs-848ff30d9074371fecc332e67848375700189d05.tar.gz
sshfs-848ff30d9074371fecc332e67848375700189d05.tar.bz2
sshfs-848ff30d9074371fecc332e67848375700189d05.zip
Dropped FAQ file
Most entries were obsolete. Useful content has been moved to the man page.
Diffstat (limited to 'sshfs.rst')
-rw-r--r--sshfs.rst11
1 files changed, 11 insertions, 0 deletions
diff --git a/sshfs.rst b/sshfs.rst
index 2553199..1239a21 100644
--- a/sshfs.rst
+++ b/sshfs.rst
@@ -242,6 +242,17 @@ someone (or something) recreates the destination file after SSHFS has
removed it, but before SSHFS had the time to rename the old file. In
this case, the rename will still fail.
+
+SSHFS hangs
+~~~~~~~~~~~
+
+In some cases, attempts to access the SSHFS mountpoint may freeze if
+no filesystem activity has occured for some time. This is typically
+caused by the SSH connection being dropped because of inactivity
+without SSHFS being informed about that. As a workaround, you can try
+to mount with ``-o ServerAliveInterval=15``. This will force the SSH
+connection to stay alive even if you have no activity.
+
See also
========