Mon Dec 1 12:27:21 GMT 2003
force user (S)
This specifies a UNIX user name that will be assigned as the default user
for all users connecting to this service. This is useful for sharing files.
You should also use it carefully as using it incorrectly can cause security
This user name only gets used once a connection is established. Thus clients
still need to connect as a valid user and supply a valid password. Once
connected, all file operations will be performed as the "forced user", no
matter what username the client connected as. This can be very useful.
In Samba 2.0.5 and above this parameter also causes the primary group of the
forced user to be used as the primary group for all file activity. Prior to
2.0.5 the primary group was left as the primary group of the connecting user
(this was a bug).
See also force group
Default: no forced user
Example: force user = auser
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 assignment. 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
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
From: Janyce Wynter [mailto:janycewynter at cnwl.igs.net]
Sent: Monday, July 01, 2002 7:34 AM
To: 'Neil Muller'
Cc: 'Samba list'
Subject: RE: FW: [Samba] Accessing Samba share with Win2k
That's not the problem.
The same usernames & passwords have been created everywhere. SEEING the
isn't the problem. The problem is that files written to the public share
be written as the user smbuser:smb, just like on the Win98 and WinME
(and not as user Janyce).
On July 2, 2002 2:56 AM, Neil Muller [SMTP:neil at neologix.net] wrote:
> On Sun, 2002-06-30 at 15:16, Janyce Wynter wrote:
> > I'll keep that under consideration (I'm a bit rusty at rpm's). But given
> > way the file ownership seems to be working, I think it's more of a Win2k
> > configuration issue. I think I need to tell my Win2K machine (blackhawk)
> > that
> > Janyce is a member of the smb group on the samba server baldeagle. (And
> > don't
> > know how to do that.)
> You need to add your user to the smbpasswd file
> eg. smbpasswd -a <username>
> If the username and password are the same as the user on your w2k
> machine and both machines are in the same workgroup and you have
> encrypted passwords enabled in smb.conf then you should be able to see
> your samba shares from w2k. See
> http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection.html (or pdf
> if you prefer).
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
To unsubscribe from this list go to the following URL and read the
More information about the samba