Index: TOSHARG-Passdb.xml
===================================================================
--- TOSHARG-Passdb.xml (revision 1008)
+++ TOSHARG-Passdb.xml (working copy)
@@ -758,7 +758,7 @@
trust accounts
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.
@@ -1051,7 +1051,7 @@
0
- Mimimum Password Length
+ Minimum Password Length
min password length
1 - 14 (Chars)
0 - 4294967295 (Chars)
@@ -1426,7 +1426,7 @@
trust account
damaged data
The manual adjustment of user, machine (workstation or server) or an inter-domain trust
- account account flgas should not be necessary under normal conditions of use of Samba. On the other hand,
+ account account flags should not be necessary under normal conditions of use of Samba. On the other hand,
where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly
useful. The tool of choice by which such correction can be affected is the pdbedit utility.
@@ -1616,9 +1616,9 @@
&rootprompt; pdbedit -P "maximum password age" -C 7776000
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
+account policy value for minimum password age is now 604800
&rootprompt; pdbedit -P "bad lockout attempt" -C 8
account policy value for bad lockout attempt was 0
account policy value for bad lockout attempt is now 8
@@ -1744,7 +1744,7 @@
lookups
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
such as that used in databases.
@@ -2635,7 +2635,7 @@
- Using OpenLDAP Overlay for Password Syncronization
+ Using OpenLDAP Overlay for Password Synchronization
Howard Chu has written a special overlay called smbk5pwd. This tool modifies the