From: David R. <ra...@ke...> - 2014-03-26 17:39:07
|
Thanks for the comments. I have gathered that what I was trying to do runs counter to the whole philosophy of sshfs. Miklos Szeredi writes: > On Tue, Mar 11, 2014 at 8:28 PM, David Raymond <ra...@ke...> wrote: > > > > I have been experimenting with using sshfs as a replacement for nfs, > > given the lack of client authentication with the latter. I start > > sshfs on the client as root with something like this in the fstab: > > > > root@gryphon:/home.gryphon /home.gryphon fuse.sshfs \ > > defaults,_netdev,allow_other,default_permissions 0 0 > > > > The allow_other allows users other than root to access files in the > > mounted file system and the default_permissions enforces server > > permissions. (UIDs and GIDs are the same on server and client.) > > This all works, but when I create a file as a non-root user, > > for example, > > > > echo "some stuff" > junk > > > > "junk" ends up with root permissions. Oops! > > > > Am I missing something? Is this a bug or a feature? Or am I > > trying to make sshfs do something it wasn't intended to do? > > Yes, sshfs is not intended for this purpose. > > You can create separate sshfs connections for each user (and run them > in separate namespaces for even better results). > > Or you could try samba. > > Thanks, > Miklos -- David J. Raymond Prof. of Physics New Mexico Tech http://www.physics.nmt.edu/~raymond/index.html |