From b44990778c50efe62df7fda762f80b49b04798f6 Mon Sep 17 00:00:00 2001
From: Volker Lendecke <vlendec@samba.org>
Date: Wed, 21 Apr 2004 12:08:44 +0000
Subject: Add smb.conf entry for "winbind nested groups" (This used to be
 commit 899ad47b18e9614bd1678bed02070e841c4be7ca)

---
 docs/smbdotconf/winbind/winbindnestedgroups.xml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 docs/smbdotconf/winbind/winbindnestedgroups.xml

(limited to 'docs/smbdotconf')

diff --git a/docs/smbdotconf/winbind/winbindnestedgroups.xml b/docs/smbdotconf/winbind/winbindnestedgroups.xml
new file mode 100644
index 0000000000..255fc9a976
--- /dev/null
+++ b/docs/smbdotconf/winbind/winbindnestedgroups.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="winbind nested groups"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://samba.org/common">
+<description>
+	<para>If set to yes, this parameter activates the support for nested
+                 groups. Nested groups are also called local groups or
+                 aliases. They work like their counterparts in Windows: Nested
+                 groups are defined locally on any machine (they are shared
+                 between DC's through their SAM) and can contain users and
+                 global groups from any trusted SAM. To be able to use nested
+                 groups, you need to run nss_winbind.</para>
+		 <para>Please note that per 3.0.3 this is a new feature, so 
+		 handle with care.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
-- 
cgit