summaryrefslogtreecommitdiff
path: root/docs/docbook/manpages
diff options
context:
space:
mode:
authorVolker Lendecke <vlendec@samba.org>2003-03-23 11:49:24 +0000
committerVolker Lendecke <vlendec@samba.org>2003-03-23 11:49:24 +0000
commitcf4f074b94052360a3e9c7d1e3d91ba8a3531212 (patch)
tree7e0c0531081d79940a2a939325e48e9879c3443d /docs/docbook/manpages
parentda7c72736af95b0bb53ad45a1b7ce157ebb04d04 (diff)
downloadsamba-cf4f074b94052360a3e9c7d1e3d91ba8a3531212.tar.gz
samba-cf4f074b94052360a3e9c7d1e3d91ba8a3531212.tar.bz2
samba-cf4f074b94052360a3e9c7d1e3d91ba8a3531212.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 6d3faeaef6c77e389d39b6d4660ffea13e7f25f2)
Diffstat (limited to 'docs/docbook/manpages')
-rw-r--r--docs/docbook/manpages/pdbedit.8.sgml26
1 files changed, 26 insertions, 0 deletions
diff --git a/docs/docbook/manpages/pdbedit.8.sgml b/docs/docbook/manpages/pdbedit.8.sgml
index 973b772374..113f23f9c4 100644
--- a/docs/docbook/manpages/pdbedit.8.sgml
+++ b/docs/docbook/manpages/pdbedit.8.sgml
@@ -31,7 +31,9 @@
<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">-g</arg>
<arg choice="opt">-d debuglevel</arg>
<arg choice="opt">-s configfile</arg>
<arg choice="opt">-P account-policy</arg>
@@ -264,6 +266,30 @@ retype new password
</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>-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>