Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Samba share set for user level access, have no problems sharing data on the share. A group called 'office' has been setup for the two users that would access the data (user - 'steve' and user - 'gail'). The users primary group has been set to 'office'
and all the files copied to the share have had the following applied.
find /home/mnsdata exec chgrp office {} \;
(changing the file group to 'office'
find /home/mnsdata exec chmod 774 {} \;
(changing the permissions of folders and files to rwxrwxr-- (774)
Great, but any new file that steve or gail saves to the 'mnsdata' folder saves with
rwxr--r-- (744). I understand that I need to apply umask xxx to each users profile
to ensure that the permissions for any new saved file will be as I wont them.
How and where do I apply umask>? Or is there another way?
Semi sorted the problem, added the two lines in the smb.conf for the specific share, works OK when saving files from the XP workstation on both accounts, but doesn't from the Windows 95 worksation on both accounts.
end up with 764 file perms and 775 folder perms from XP machine and 744 from the Win95 machine, as though the 95 machine ignores the settings. It all seems a little mixed.
Any ideas to test? Do I need to apply something else when logging connecting from a Win95 machine?
Now that is really weird as setting the permissions is not something that the client machine actually see's happening. The smb.conf man page does say (about force directory mode") that
Quote:
This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory
created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a directory that
is being created
which would suggest to me that these setting will always add to the permissions, so if the dir is being created as 0700 or 0711 it will always end up as 0755. Take a look at the descriptions of the following parameters in the smb.conf man page, I'm sure that one combination must do the job!
force create mode
force directory mode
force directory
force security mode
security mask
Sorry that I can't provide any more useful suggestions this isn't a behaviour I've ever seen (or ever realised was there).
Sorry I have taken so long to get back and thanks for your help on this one.
Used the following on the samba share:
force create mode = 0755
force directory mode = 0755
gives me a rwxrwxr-- on all files by the two members of the office group and for the moment that will do me. I will have a play and refine this when I have got to grips with file permissions. I am really looking to get rwxrwx--- so that only the owner and the group have access to any files.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.