My usage scenario: A server contains a directory owned by group
'collab', which is group writeable and has  the setgid bit set. This
means that all new directories created underneath it will also be owned
by group 'collab'. The server is set up with accounts for users whose
desktop systems automatically mount this directory using sshfs so that
it appears on their local desktop. The idea is that everyone who is in
the 'collab' group on the server should be able to add and delete files
and directories from this folder. The umask on each user's desktop
system must be set to create all new files and directories group-
writeable, which this bug prevents from happening correctly. As a
result, a new directory created by a user using Hardy isn't writeable by
the other members of the 'collab' group until the group permission is
manually corrected. Please let me know if anything here doesn't make
sense. I think it's a fairly sensible usage scenario.

-- 
Nautilus and other gnome apps using incorrect umask for new directories
https://bugs.launchpad.net/bugs/242618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to