Changeset 274 for branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml

Timestamp:

Jun 17, 2009, 2:19:52 PM (16 years ago)

Author:

Herwig Bauernfeind

Message:

Update 3.3 branch to 3.3.5

File:

• branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml (modified) (5 diffs)

branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml

@@ -758 +758 @@
                 The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba.
                 Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
-                them. A user account and a machine account are indistinquishable from each other, except that
+                them. A user account and a machine account are indistinguishable from each other, except that
                 the machine account ends in a $ character, as do trust accounts.
                 </para>
@@ -1051 +1051 @@
                     </row>
                     <row>
-                                        <entry><para>Mimimum Password Length</para></entry>
+                                        <entry><para>Minimum Password Length</para></entry>
                                         <entry><para>min password length</para></entry>
                                         <entry><para>1 - 14 (Chars)</para></entry>
@@ -1616 +1616 @@
 account policy value for maximum password age was 4294967295
 account policy value for maximum password age is now 7776000
-&rootprompt; pdbedit -P "minimum password age" -C 7
+&rootprompt; pdbedit -P "minimum password age" -C 604800
 account policy value for minimum password age was 0
 account policy value for minimum password age is now 7
@@ -1736 +1736 @@
 <indexterm><primary>lookups</primary></indexterm>
                 The first problem is that all lookups must be performed sequentially. Given that
-                there are approximately two lookups per domain logon (one during intial logon validation
+                there are approximately two lookups per domain logon (one during initial logon validation
                 and one for a session connection setup, such as when mapping a network drive or printer), this
                 is a performance bottleneck for large sites. What is needed is an indexed approach
@@ -2627 +2627 @@
 
                 <sect3>
-                <title>Using OpenLDAP Overlay for Password Syncronization</title>
+                <title>Using OpenLDAP Overlay for Password Synchronization</title>
 
                 <para>