The branch, master has been updated
via ab09fcf1da51451b666f962a418051581fb4e78e (commit)
from 55a9ea2b33cbcd39ae44972b71922c9c87748d75 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit ab09fcf1da51451b666f962a418051581fb4e78e
Author: OPC oota <[email protected]>
Date: Mon Sep 14 02:44:04 2009 +0200
s3:docs: Fix a typo
-----------------------------------------------------------------------
Summary of changes:
docs-xml/Samba3-HOWTO/TOSHARG-Group-Mapping.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Changeset truncated at 500 lines:
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Group-Mapping.xml
b/docs-xml/Samba3-HOWTO/TOSHARG-Group-Mapping.xml
index 337ae3d..e2a0abc 100644
--- a/docs-xml/Samba3-HOWTO/TOSHARG-Group-Mapping.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Group-Mapping.xml
@@ -810,7 +810,7 @@ net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d
Versions of Samba-3 prior to 3.0.23 automatically create default group
mapping for the
<literal>Domain Admins, Domain Users</literal> and <literal>Domain
Guests</literal> Windows
groups, but do not map them to UNIX GIDs. This was a cause of
administrative confusion and
- trouble. Commencing with Samba-3.0.23 this annomaly has been fixed -
thus all Windows groups
+ trouble. Commencing with Samba-3.0.23 this anomaly has been fixed -
thus all Windows groups
must now be manually and explicitly created and mapped to a valid UNIX
GID by the Samba
administrator.
</para></note>
--
Samba Shared Repository
