From 56d6030f9cc2a90ace2f04f3dc4611ea06737b89 Mon Sep 17 00:00:00 2001 From: Nikolaus Rath Date: Tue, 20 Jun 2017 16:10:49 -0700 Subject: Document hardlink limitation. --- README.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'README.rst') diff --git a/README.rst b/README.rst index 943d12f..0a536a6 100644 --- a/README.rst +++ b/README.rst @@ -88,6 +88,9 @@ the sshfs developers know! Caveats ------- +Rename +~~~~~~ + Some SSH servers do not support atomically overwriting the destination when renaming a file. In this case you will get an error when you attempt to rename a file and the destination already exists. A @@ -98,6 +101,14 @@ 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. +Hardlinks +~~~~~~~~~ + +If the SSH server supports the *hardlinks* extension, SSHFS will allow +you to create hardlinks. However, hardlinks will always appear as +individual files when seen through an SSHFS mount, i.e. they will +appear to have different inodes and an *st_nlink* value of 1. + Getting Help ------------ -- cgit v1.2.3