Changes between Version 48 and Version 49 of SftpFrontend
- Timestamp:
- 2010-06-29T01:20:09Z (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SftpFrontend
v48 v49 56 56 If a file is written via two handles concurrently, the contents visible at any point in time will be the data written via one handle or the other (or the previous contents), ''or'' the read will fail. The result will not be an interleaving as would be the case for a POSIX filesystem. Also, the file contents obtained by a ''successful'' read via any handle will be a snapshot at about the time of the open. These differences from the POSIX semantics are arguably improvements (at least when the read succeeds), but in principle they could confuse some applications. 57 57 58 If a file in a mutable directory is closed concurrently with an operation that needs to read the directory, then the latter operation may fail . (#1105)58 If a file in a mutable directory is closed concurrently with an operation that needs to read the directory, then the latter operation may fail (#1105). 59 59 60 60 The MacFUSE version of sshfs stores "extended attributes" in files with names starting with "{{{._}}}". For example the attributes for "{{{foo.txt}}}" would be stored in a file called "{{{._foo.txt}}}". Since some Mac OS X applications may depend on these attributes (especially for their own file formats), if you need to copy or move the original file then you should copy or move the attribute file along with it. The OS X {{{cp}}} and {{{mv}}} commands will do this by default; operations using the Tahoe WUI or CLI will not (unless you are moving all files in a directory). Note that filenames beginning with "{{{.}}}" are not listed by default by {{{ls}}}.
