valid point... my editor doesn't set a temp file :) "Gally, Jerry" <[email protected]> wrote on 04/19/2011 01:41:48 PM:
> > But not on the editor's temp file ... > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Tuesday, April 19, 2011 11:39 AM > To: Gally, Jerry > Cc: [email protected]; [email protected] > Subject: Re: [Gluster-users] gluster mounted volumes not following > group permissions > > > step 3 manually sets the mode to allow group write. > > -greg > > [email protected] wrote on 04/19/2011 01:35:41 PM: > > > > > I presume that would be caused by a user1's umask setting that does > > not set group write permissions on newly created files. > > > > -----Original Message----- > > From: [email protected] [mailto:gluster-users- > > [email protected]] On Behalf Of Whit Blauvelt > > Sent: Tuesday, April 19, 2011 11:30 AM > > To: [email protected] > > Cc: [email protected] > > Subject: Re: [Gluster-users] gluster mounted volumes not following > > group permissions > > > > Greg, > > > > I've just verified your report by doing the same test with 3.1.4 in an > > Ubuntu 10.10 server environment, with the client mount via NFS from > Ubuntu > > 8.04.4. I get exactly the same result. In this case a file is first > written > > by user1, member of "staff" group. Then user2 opens it, adds an edit, and > > tries to save. The backup (using the joe editor) shows up with user2's > > ownership: > > > > -rw-rw-r-- 1 user1 staff 4 2011-04-19 14:23 dog > > -rw-r--r-- 1 user2 staff 4 2011-04-19 14:24 dog~ > > > > But the save fails with "Error opening file" from the editor. > > > > Whit > > > > > > On Tue, Apr 19, 2011 at 01:19:28PM -0500, [email protected] > wrote: > > > > > > I just had it pointed out to me that we are experiencing situations > where a > > > process that has group write permissions on a file is failing for not > > > actually having write permissions. I broke it down to the most simple > of > > > tests: > > > > > > userA creates file 'test' in /mnt/gluster/ > > > userA sets group ownership to groupA on /mnt/gluster/test > > > userA sets mode to 664 on /mnt/gluster/test > > > userA tries to edit /mnt/gluster/test and succeeds > > > > > > root ensures that userB is in groupA > > > userB tries to edit /mnt/gluster/test and FAILS > > > > > > Anyone else ever seen something like this? > > > > > > We're on 3.1.2 in a RHEL 5 environment. > > > > > > -greg > > _______________________________________________ > > Gluster-users mailing list > > [email protected] > > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > > _______________________________________________ > > Gluster-users mailing list > > [email protected] > > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
