Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
in [global] I have:
guest account = nobody
guest ok = yes
guest only = no
read only = no
my shared resource named "example" is defined like this:
[example]
path = /home/user/shared
comment = my shared resource
browseable = yes
read only = no
writable = yes
guest ok = yes
guest only = no
create mask = 0777
directory mask = 0777
I have a problem .... when a guest user creates a file in "example" , its does NOT get 0777 permision.
What I want is that when a guest user creates a file or directory in the "example" share, the file or directory to have ALL PERSMISIONS FOR EVERYBODY ,,.... like this "a+rwx"
Maybe my mistake is that I am not understanding something.
I believe that create mask = 0777 would do the "chmod a+rwx file/dir" , maybe not ................ HELP!!!!!!!!!!!!!!!!!
Last edited by fachamix; 11-15-2009 at 01:16 PM.
Reason: bad title
I also faced same problem few days back. After investigation i concluded that ' create mask ' parameter also care whats you ' umask ' permission settings. If you want to avoid 'umask ' value thenm ' force create mode ' will be right choice .
I will try the force create mode or force create mask and after that I will tell you people.
whats the umask ?????? I am newbie ???? (umask is the LINUX permision for a directory/file ?)
Suppose you are creating a file or directory what permission get applied on that? 'umask determine that' suppose your umask value is 022 , then when you create a new folder the permission on that will be 755(drwxr-xr-x). i mean 777-022=755. You can check umask value using umask
command, and you can also change that value. For more help type man umask on your system
I was also talking about linux umask i mean 'man umask'(nothing about create mask). I just want to say set create mask depend on what is umask value in linux permission.
'force create mode =777' in smb.conf share section will surely done his job. No need to alter any value in mask parameters.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.