ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-19 04:57:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

FTP-and-SFTP.txt: minor technical correction to doc for 'no-write' flag.

Browse Source
This commit is contained in:
david-sarah 2010-06-06 23:16:00 -07:00
parent 8b014372b1
commit d7d0ae3c2c
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/frontends/FTP-and-SFTP.txt
View File

@ -183,10 +183,10 @@ caps to it will remain valid. (See docs/garbage-collection.txt for how to
reclaim the space used by files that are no longer needed.)
The 'no-write' metadata field of a directory entry can override this
behaviour. If the 'no-write' field holds a non-empty string (typically
"true"), then a permission error will occur when trying to write to the
file, even if it is in a writeable directory. This does not prevent the
directory entry from being unlinked or replaced.
behaviour. If the 'no-write' field holds a true value, then a permission
error will occur when trying to write to the file, even if it is in a
writeable directory. This does not prevent the directory entry from being
unlinked or replaced.
When using sshfs, the 'no-write' field can be set by clearing the 'w'
bits in the Unix permissions, for example using the command