From 705db2effac38df9aaefa9cc6baa9614207b26af Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Mon, 7 Apr 2003 13:51:11 +0000 Subject: - Add &author.mimir; entity - Several smaller layout and typo fixes (This used to be commit 96aa93ea4f56ef069c3127547296581f8e0ce3bd) --- docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml') diff --git a/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml b/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml index 8aea87fe24..e037da4aeb 100644 --- a/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml +++ b/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml @@ -11,12 +11,12 @@ Starting with Samba 3.0 alpha 2, a new group mapping function is available. The current method (likely to change) to manage the groups is a new command called -smbgroupedit. +&smbgroupedit;. The first immediate reason to use the group mapping on a PDC, is that -the domain admin group of smb.conf is +the domain admin group of &smb.conf; is now gone. This parameter was used to give the listed users local admin rights on their workstations. It was some magic stuff that simply worked but didn't scale very well for complex setups. @@ -71,7 +71,7 @@ give access to a certain directory to some users who are member of a group on your samba PDC. Flag that group as a domain group by running: -smbgroupedit -a unixgroup -td +smbgroupedit -a unixgroup -td You can list the various groups in the mapping database like this smbgroupedit -v -- cgit