summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorVolker Lendecke <vlendec@samba.org>2003-03-23 11:50:16 +0000
committerVolker Lendecke <vlendec@samba.org>2003-03-23 11:50:16 +0000
commitb8d83f7cdb5aed2bdcc185388f148e2fe4726bf8 (patch)
tree94d48f65a20f05fef839fb89cbd3de3339e302a1 /docs
parenteaf3fbe642d3c84fa5aeaacb11f9676a05a26b31 (diff)
downloadsamba-b8d83f7cdb5aed2bdcc185388f148e2fe4726bf8.tar.gz
samba-b8d83f7cdb5aed2bdcc185388f148e2fe4726bf8.tar.bz2
samba-b8d83f7cdb5aed2bdcc185388f148e2fe4726bf8.zip
This does two things:
* pdbedit -i -e sets all SAM_ACCOUNT elements to CHANGED to satisfy the new pdb_ldap.c handling * pdbedit -g transfers group mappings. I made this separate from the user database, as current installations have to live with a split backend. So, if you are running 3_0 alphas with LDAP as a backend and upgrade to the next 3_0 alpha, you should call pdbedit -i tdbsam -e ldapsam -g to transfer your group mapping database to LDAP. You certainly have to have all your groups as posixGroup objects in LDAP and adapt the LDAP schema before this call. Volker (This used to be commit 09a3db0ffcbbe578788d3dd5ee7540d27cc7c09a)
Diffstat (limited to 'docs')
-rw-r--r--docs/docbook/manpages/pdbedit.8.sgml13
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/docbook/manpages/pdbedit.8.sgml b/docs/docbook/manpages/pdbedit.8.sgml
index 1484bfec9a..2457d899de 100644
--- a/docs/docbook/manpages/pdbedit.8.sgml
+++ b/docs/docbook/manpages/pdbedit.8.sgml
@@ -31,6 +31,7 @@
<arg choice="opt">-x</arg>
<arg choice="opt">-i passdb-backend</arg>
<arg choice="opt">-e passdb-backend</arg>
+ <arg choice="opt">-g</arg>
<arg choice="opt">-b passdb-backend</arg>
<arg choice="opt">-d debuglevel</arg>
<arg choice="opt">-s configfile</arg>
@@ -266,6 +267,18 @@
</varlistentry>
<varlistentry>
+ <term>-g</term>
+ <listitem><para>If you specify <parameter>-g</parameter>,
+ then <parameter>-i in-backend -e out-backend</parameter>
+ applies to the group mapping instead of the user database.
+
+ <para>This option will ease migration from one passdb backend to
+ another and will ease backing up.</para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term>-b passdb-backend</term>
<listitem><para>Use a different default passdb backend. </para>