Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Below is my smb.conf file made with Webmin on RH 8.0. I am having an issue where files that are created on the SAMBA server have different group ownerships. Some have user.group ownership of "ghight.ghight" and others have "ghight.smbadmin". I am a member of both groups. Why does it seems to randomly pick group ownership for my files? All of these are created from a Win98 workstation so me changing groups isn't an issue.
Any thoughts would be helpful and appreciated.
PS-What you see is what you get. Nothing has been deleted or changed in the conf file.
log file = /var/log/samba/%m.log
dns proxy = no
smb passwd file = /etc/samba/smbpasswd
server string = Job Archives
obey pam restrictions = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
workgroup = 3IENG
hosts allow = 192.168.1. 127.
encrypt passwords = yes
security = user
max log size = 0
preserve case = yes
write list = ghight,nzimmer,troedel,bzimmer,@smbadmin
path = /home/archives
comment = Archive of completed job files
create mode = 775
directory mode = 775
comment = Modified files should be submitted here
writeable = yes
create mode = 775
path = /home/submit
directory mode = 775
From smb.conf man page force group (S)
This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service.
This is useful for sharing files by ensuring that all access to files on service will use the named group for their permissions
checking. Thus, by assigning permissions for this group to the files and directories within this service the Samba administrator
can restrict or allow sharing of these files.
In Samba 2.0.5 and above this parameter has extended functionality in the following way. If the group name listed here has a '+'
character prepended to it then the current user accessing the share only has the primary group default assigned to this group if
they are already assigned as a member of that group. This allows an administrator to decide that only users who are already in a
particular group will create files with group ownership set to that group. This gives a finer granularity of ownership assign-
ment. For example, the setting force group = +sys means that only users who are already in group sys will have their default
primary group assigned to sys when accessing this Samba share. All other users will retain their ordinary primary group.
If the force user parameter is also set the group specified in force group will override the primary group set in force user.
See also force user.
Default: no forced group
Example: force group = agroup
I don't know wether using %G will work but it might be worth a go, so
force group = %G
would force the group to always be the *primary* group of the user who is connected to the share.
Originally posted by jharris For example, the setting force group = +sys means that only users who are already in group sys will have their default primary group assigned to sys when accessing this Samba share.
force group = +smbadmin
would make everyone in the smbadmin group use those right instead of the regular primary group? This is still a question, I'm not real sure.
ps-Thanks for the post. I honestly didn't get that far into the man page.