On Tue, 21 Jul 2009, Sam Hocevar wrote: > When using eg. umask=002, instead of using the information to control > permissions of new files, sshfs makes all remote files appear as > executable locally.
This is how this option is supposed to work. The README in the fuse package says about the 'umask' option: umask=M Override the permission bits in 'st_mode' set by the filesystem. The resulting permission bits are the ones missing from the given umask value. The value is given in octal representation. This may be confusing, and so it probably should be explicitly mentioned in the sshfs man page. Thanks, Miklos -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
