diff options
| author | Nikolaus Rath <Nikolaus@rath.org> | 2017-06-06 16:34:02 -0400 |
|---|---|---|
| committer | Nikolaus Rath <Nikolaus@rath.org> | 2017-06-06 16:45:15 -0400 |
| commit | 9f2eb0437104641bcea46dad3d4adcc2c4dd442f (patch) | |
| tree | d009811cc3fb54de7c15907509d007371b2abb2c /README.md | |
| parent | 6c301e043b14db7215d5a8be7d491a981f861ebd (diff) | |
| download | sshfs-9f2eb0437104641bcea46dad3d4adcc2c4dd442f.tar sshfs-9f2eb0437104641bcea46dad3d4adcc2c4dd442f.tar.gz sshfs-9f2eb0437104641bcea46dad3d4adcc2c4dd442f.tar.bz2 sshfs-9f2eb0437104641bcea46dad3d4adcc2c4dd442f.zip | |
Document rename workaround.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -88,6 +88,21 @@ the sshfs developers know! make sudo make install + +Caveats +------- + +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 +workaround is to first remove the destination file, and then do the +rename. SSHFS can do this automatically if you call it with `-o +workaround=rename`. However, in this case it is still possible that +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. + + Getting Help ------------ |