diff options
| author | Nikolaus Rath <Nikolaus@rath.org> | 2017-06-20 16:10:49 -0700 |
|---|---|---|
| committer | Nikolaus Rath <Nikolaus@rath.org> | 2017-07-12 17:10:17 +0200 |
| commit | 63e65aeaeb30bdadbb342bde6094c3a77cbd3070 (patch) | |
| tree | a338224793f501c2ec9b7198e5cf94be0d8eb156 /README.rst | |
| parent | 70575040b4eb46bc797b28462e2f42dde364a09a (diff) | |
| download | sshfs-63e65aeaeb30bdadbb342bde6094c3a77cbd3070.tar sshfs-63e65aeaeb30bdadbb342bde6094c3a77cbd3070.tar.gz sshfs-63e65aeaeb30bdadbb342bde6094c3a77cbd3070.tar.bz2 sshfs-63e65aeaeb30bdadbb342bde6094c3a77cbd3070.zip | |
Document hardlink limitation.
Diffstat (limited to 'README.rst')
| -rw-r--r-- | README.rst | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -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 ------------ |