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

Timestamp:

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

Author:

Herwig Bauernfeind

Message:

Update 3.3 branch to 3.3.5

Location:

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

Files:

• TOSHARG-FastStart.xml (modified) (2 diffs)
• TOSHARG-Install.xml (modified) (5 diffs)
• TOSHARG-PDC.xml (modified) (2 diffs)
• TOSHARG-Passdb.xml (modified) (5 diffs)
• TOSHARG-VFS.xml (modified) (1 diff)
• TOSHARG-foreword-cargill.xml (modified) (1 diff)
• index.xml (modified) (1 diff)
• manpages.xml (modified) (1 diff)

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

@@ -1215 +1215 @@
 <smbconfoption name="ldap group suffix">ou=People</smbconfoption>
 <smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=Manager</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=Manager,dc=quenya,dc=org</smbconfoption>
 <smbconfoption name="ldap ssl">no</smbconfoption>
 <smbconfoption name="ldap passwd sync">Yes</smbconfoption>
@@ -1282 +1282 @@
 <smbconfoption name="ldap group suffix">ou=People</smbconfoption>
 <smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=Manager</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=Manager,dc=quenya,dc=org</smbconfoption>
 <smbconfoption name="ldap ssl">no</smbconfoption>
 <smbconfoption name="ldap passwd sync">Yes</smbconfoption>

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

@@ -335 +335 @@
                 <varlistentry><term>nmbd</term>
                         <listitem><para>
-                        <indexterm><primary>smbd</primary></indexterm>
-                        <indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
+                        <indexterm><primary>nmbd</primary></indexterm>
+                        <indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
                         This daemon handles all name registration and resolution requests. It is the primary vehicle involved
                         in network browsing. It handles all UDP-based protocols. The <command>nmbd</command> daemon should
@@ -345 +345 @@
                 <varlistentry><term>smbd</term>
                         <listitem><para>
-                        <indexterm><primary>nmbd</primary></indexterm>
-                        <indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
+                        <indexterm><primary>smbd</primary></indexterm>
+                        <indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
                         This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
                         manages local authentication. It should be started immediately following the startup of <command>nmbd</command>.
@@ -468 +468 @@
         be adopted is to do all documentation and configuration in a file that has another name, such as
         <filename>smb.conf.master</filename>. The <command>testparm</command> utility can be used to generate a
-        fully optimized &smb.conf; file from this master configuration and documtenation file as shown here:
+        fully optimized &smb.conf; file from this master configuration and documentation file as shown here:
 <screen>
 &rootprompt; testparm -s smb.conf.master > smb.conf
@@ -485 +485 @@
         <indexterm><primary>swat</primary></indexterm>
         SWAT is a Web-based interface that can be used to facilitate the configuration of Samba.  SWAT might not
-        be available in the Samba package that shipped with your platform, but in a separate package. If it is
-        necesaary to built SWAT please read the SWAT man page regarding compilation, installation, and
+        be available in the Samba package that shipped with your platform, but in a separate package. If you need to build SWAT please read the SWAT man page regarding compilation, installation, and
         configuration of SWAT from the source code.
         </para>
@@ -499 +498 @@
         <para>
         SWAT can be used from a browser on any IP-connected machine, but be aware that connecting from a remote
-        machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear. 
-        </para>
-
-        <para>
+        machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear.
+        </para>
+
+        <para>
+        Please note that re-writing the configuration file using SWAT will
+        remove all comments!
         More information about SWAT can be found in <link linkend="SWAT">The Samba Web Administration Tool</link>.
         </para>

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

@@ -307 +307 @@
 SSO implementations utilize centralization of all user account information. Depending on environmental
 complexity and the age of the systems over which a SSO solution is implemented, it may not be possible to
-change the solution architecture so as to accomodate a new identity management and user authentication system.
+change the solution architecture so as to accommodate a new identity management and user authentication system.
 Many SSO solutions involving legacy systems consist of a new super-structure that handles authentication on
 behalf of the user. The software that gets layered over the old system may simply implement a proxy
@@ -376 +376 @@
 alternative specification called WS-Security. Some believe that the competing technologies and methods may
 converge when the SAML 2.0 standard is introduced. A few Web access-management products support SAML today,
-but implemention of the technology mostly requires customization to integrate applications and develop user
-interfaces. In a nust-shell, that is why FIM is a big and growing industry.
+but implementation of the technology mostly requires customization to integrate applications and develop user
+interfaces. In a nutshell, that is why FIM is a big and growing industry.
 </para>
 

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>

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

@@ -277 +277 @@
                 <para>
 <indexterm><primary>logging</primary></indexterm>
-                This auditing tool is more felxible than most people readily will recognize. There are a number of ways
+                This auditing tool is more flexible than most people will readily recognize. There are a number of ways
                 by which useful logging information can be recorded.
                 </para>

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

@@ -39 +39 @@
 <para>
 A <emphasis>good standard</emphasis> survives because people know how to use it. People know how to use a
-standard when it is so transparent, so obvious, and so easy that it become invisible. And a standard becomes
+standard when it is so transparent, so obvious, and so easy that it becomes invisible. And a standard becomes
 invisible only when the documentation describing how to deploy it is clear, unambiguous, and correct. These
 three elements must be present for a standard to be useful, allowing communication and interaction between two

branches/samba-3.3.x/docs-xml/Samba3-HOWTO/index.xml

@@ -4 +4 @@
 <book id="Samba-HOWTO-Collection"
         xmlns:xi="http://www.w3.org/2003/XInclude">
-<title>The Official Samba 3.2.x HOWTO and Reference Guide</title>
+<title>The Official Samba 3.3.x HOWTO and Reference Guide</title>
 
 <bookinfo>

branches/samba-3.3.x/docs-xml/Samba3-HOWTO/manpages.xml

@@ -23 +23 @@
         <xi:include href="../manpages-3/nmblookup.1.xml"/>
         <xi:include href="../manpages-3/ntlm_auth.1.xml"/>
-        <xi:include href="../manpages-3/pam_winbind.7.xml"/>
+        <xi:include href="../manpages-3/pam_winbind.8.xml"/>
         <xi:include href="../manpages-3/pdbedit.8.xml"/>
         <xi:include href="../manpages-3/profiles.1.xml"/>