Joe Pfaltzgraff@PATAPSCO 10/11/2001 11:37 AM It appears that if a share has "inherit permissions = true" and the directory permissions are 0660, then the user cannot set any file in the directory read-only. When the file is first created its permissions are 0660. If the user then goes into the properties dialog box and checks read-only, the permissions do not change. Is this a bug? IMO the user should be able to set it to read-only, and the "inherit permissions" should only govern the creation of new files. If it is not a bug, is there a way to get around this, without removing "inherit permissions" and without chmod at the shell? Thanks, Joe Pfaltzgraff
Joe Pfaltzgraff@PATAPSCO 10/17/2001 08:30 AM It appears that if a share has "inherit permissions = true" and the directory permissions are 0660, then the user cannot set any file in the directory read-only. When the file is first created its permissions are 0660. If the user then goes into the properties dialog box and checks read-only, the permissions do not change. Is this a bug? IMO the user should be able to set it to read-only, and the "inherit permissions" should only govern the creation of new files. If it is not a bug, is there a way to get around this, without removing "inherit permissions" and without chmod at the shell? Thanks, Joe Pfaltzgraff
On Wed, 17 Oct 2001 Joe_Pfaltzgraff@patapsco.com wrote:> It appears that if a share has "inherit permissions = true" and the > directory permissions are 0660, then the user cannot set any file in > the directory read-only. When the file is first created its > permissions are 0660. If the user then goes into the properties > dialog box and checks read-only, the permissions do not change. Is > this a bug? IMO the user should be able to set it to read-only, and > the "inherit permissions" should only govern the creation of new > files. If it is not a bug, is there a way to get around this, without > removing "inherit permissions" and without chmod at the shell?Sounds like a bug to me. What version are you running? cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
Joe Pfaltzgraff@PATAPSCO 10/17/2001 01:28 PM I was using 2.2.0 when I noticed the problem. Since then I upgraded to 2.2.1a, and the problem still exists. I haven't had the chance to check out 2.2.2. "Gerald (Jerry) Carter" <jerry@samba.org> on 10/17/2001 10:23:13 AM To: Joe Pfaltzgraff/Patapsco@Patapsco cc: samba@samba.org Subject: Re: inherit permissions + read-only On Wed, 17 Oct 2001 Joe_Pfaltzgraff@patapsco.com wrote:> It appears that if a share has "inherit permissions = true" and the > directory permissions are 0660, then the user cannot set any file in > the directory read-only. When the file is first created its > permissions are 0660. If the user then goes into the properties > dialog box and checks read-only, the permissions do not change. Is > this a bug? IMO the user should be able to set it to read-only, and > the "inherit permissions" should only govern the creation of new > files. If it is not a bug, is there a way to get around this, without > removing "inherit permissions" and without chmod at the shell?Sounds like a bug to me. What version are you running? cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba