diff options
| -rw-r--r-- | docs/docbook/projdoc/NT4Migration.sgml | 18 | ||||
| -rw-r--r-- | docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml | 2 | ||||
| -rw-r--r-- | docs/docbook/projdoc/PolicyMgmt.sgml | 2 | ||||
| -rw-r--r-- | docs/docbook/projdoc/Portability.sgml | 1 | ||||
| -rw-r--r-- | docs/docbook/projdoc/SWAT.sgml | 2 | 
5 files changed, 14 insertions, 11 deletions
diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml index 60d9f121f4..469215e32e 100644 --- a/docs/docbook/projdoc/NT4Migration.sgml +++ b/docs/docbook/projdoc/NT4Migration.sgml @@ -79,19 +79,19 @@ What are the features that Samba-3 can NOT provide?  <itemizedlist>  <listitem> -	<para>Active Directory Server<para> +	<para>Active Directory Server</para>  </listitem>  <listitem> -	<para>Group Policy Objects (in Active Direcrtory)<para> +	<para>Group Policy Objects (in Active Direcrtory)</para>  </listitem>  <listitem> -	<para>Machine Policy objects<para> +	<para>Machine Policy objects</para>  </listitem>  <listitem> -	<para>Logon Scripts in Active Directorty<para> +	<para>Logon Scripts in Active Directorty</para>  </listitem>  <listitem> -	<para>Software Application and Access Controls in Active Directory<para> +	<para>Software Application and Access Controls in Active Directory</para>  </listitem>  </itemizedlist> @@ -309,7 +309,7 @@ Samba-3 set up as a DC with netlogon share, profile share, etc.  	<step><para>initGrps.sh DOMNAME</para></step> -	<step><para>smbgroupedit -v</para> +	<step><para>net groupmap list</para>  		<substeps><step><para>Now check that all groups are recognised</para></step></substeps>  	</step> @@ -469,7 +469,7 @@ Logon Scripts (Know how they work)  User and Group mapping to Unix/Linux  	username map facility may be needed -	Use smbgroupedit to connect NT4 groups to Unix groups +	Use 'net groupmap' to connect NT4 groups to Unix groups  	Use pdbedit to set/change user configuration  NOTE:  If migrating to LDAP back end it may be easier to dump initial LDAP database to LDIF, then edit, then reload into LDAP @@ -489,7 +489,7 @@ Migration Tools  	Profiles, Policies, Access Controls, Security  Migration Tools -	Samba: net, rpcclient, smbpasswd, pdbedit, smbgroupedit, profiles +	Samba: net, rpcclient, smbpasswd, pdbedit, profiles  	Windows: NT4 Domain User Manager, Server Manager (NEXUS)  Authentication @@ -497,6 +497,8 @@ Authentication  </programlisting>  </para> +</sect2> +  </sect1>  </chapter> diff --git a/docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml b/docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml index a95baf0281..395bd71a27 100644 --- a/docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml +++ b/docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml @@ -244,7 +244,7 @@ Options recognized by this module are as follows:                                  password used for successful authentication.          smbconf=< file >  -     specify an alternate path to the smb.conf                                  file. -</programlisting><para> +</programlisting></para>  <para><programlisting>  Thanks go to the following people: diff --git a/docs/docbook/projdoc/PolicyMgmt.sgml b/docs/docbook/projdoc/PolicyMgmt.sgml index 7557d496a4..9ec9d452a7 100644 --- a/docs/docbook/projdoc/PolicyMgmt.sgml +++ b/docs/docbook/projdoc/PolicyMgmt.sgml @@ -310,7 +310,7 @@ Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC  <para>  With a Samba Domain Controller, the new tools for managing of user account and policy information includes: -<filename>smbpasswd, pdbedit, smbgroupedit, net, rpcclient.</filename>. The administrator should read the +<filename>smbpasswd, pdbedit, net, rpcclient.</filename>. The administrator should read the  man pages for these tools and become familiar with their use.  </para> diff --git a/docs/docbook/projdoc/Portability.sgml b/docs/docbook/projdoc/Portability.sgml index cc21ecf255..72c3d20547 100644 --- a/docs/docbook/projdoc/Portability.sgml +++ b/docs/docbook/projdoc/Portability.sgml @@ -229,6 +229,7 @@ Nsswitch on Solaris 9 refuses to use the winbind nss module.  This behavior  is fixed by Sun in patch 113476-05 which as of March 2003 is not in any  roll-up packages.  </para> +</sect2>  </sect1>  </chapter> diff --git a/docs/docbook/projdoc/SWAT.sgml b/docs/docbook/projdoc/SWAT.sgml index 751138f138..0aea999b53 100644 --- a/docs/docbook/projdoc/SWAT.sgml +++ b/docs/docbook/projdoc/SWAT.sgml @@ -134,7 +134,7 @@ Modifications to the swat setup are as following:  	root# /usr/bin/openssl req -new -x509 -days 365 -nodes -config \  	 	/usr/share/doc/packages/stunnel/stunnel.cnf \  		-out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem -	</programlisting><para></listitem> +	</programlisting></para></listitem>  	<listitem><para>  	remove swat-entry from [x]inetd   | 
