Bug 2317 - Directory Mask saved wrong in config using swat
Summary: Directory Mask saved wrong in config using swat
Status: RESOLVED WONTFIX
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: SWAT (show other bugs)
Version: 3.0.11
Hardware: x86 Windows XP
: P3 minor
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-07 06:00 UTC by Alexander Blüm
Modified: 2007-03-06 05:32 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Blüm 2005-02-07 06:00:41 UTC
I have a share where different users may write to it and create directories and
files.. the thing is, I want newly created directories to to have the stickybit
- like 1770, but now when I add the "directory mask" under "security options"
and commit, then swat prefixes a zero to the mode - 01770.. and when I change
the first zero to a one, then again a zero is prefixed, so a mode of 011770 is
created... and so on... nothing happens, the directories created still have the
same permissions as before and no stickybit is set...

also samba seems to ignore the "1770" modes in its own config. no directory is
ever created with that mode... 

looks like a bug to me.
Comment 1 Lars Müller 2005-02-07 08:21:12 UTC
As a workaround please use 'inherit permissions = Yes'.

But it might even better to use filesystem ACLs and 'inherit acls = Yes'.

I move it to 3.0.11 as it's still valid there.
Comment 2 Karolin Seeger 2007-03-06 05:28:11 UTC
Please try to set 'force directory mode = 01770' in addition to 'directory mask = 01770'. It works for me. 
The leading '0' does not derange. 
Comment 3 Karolin Seeger 2007-03-06 05:32:46 UTC
Closing the bug report. 
Please reopen if it is still an issue for you.