Another set of updates.

(This used to be commit 5fc92d4596956ad7a2f099276fb529d0ba28d10b)

1 files changed, 148 insertions, 47 deletions

diff --git a/docs/docbook/projdoc/UNIX_INSTALL.xml b/docs/docbook/projdoc/UNIX_INSTALL.xml
index 39fac749b9..3dff9a5528 100644
--- a/docs/docbook/projdoc/UNIX_INSTALL.xml
+++ b/docs/docbook/projdoc/UNIX_INSTALL.xml
@@ -13,7 +13,8 @@
 <sect1>
 	<title>Obtaining and installing samba</title>
 
-	<para>Binary packages of samba are included in almost any Linux or 
+	<para>
+	Binary packages of samba are included in almost any Linux or
 	Unix distribution. There are also some packages available at 
 	<ulink url="http://samba.org/">the samba homepage</ulink>.
 	</para>
@@ -29,67 +30,80 @@
 </sect1>
 
 <sect1>
-	<title>Configuring samba</title>
+	<title>Configuring samba (smb.conf)</title>
 
-	<para>Samba's configuration is stored in the smb.conf file, 
+	<para>
+	Samba's configuration is stored in the smb.conf file, 
 	that usually resides in <filename>/etc/samba/smb.conf</filename> 
 	or <filename>/usr/local/samba/lib/smb.conf</filename>. You can either 
 	edit this file yourself or do it using one of the many graphical 
 	tools that are available, such as the web-based interface swat, that 
-	is included with samba.</para>
+	is included with samba.
+	</para>
 	
 <sect2>
-	<title>Editing the <filename>smb.conf</filename> file</title>
+	<title>Example Configuration</title>
 	
-	<para>There are sample configuration files in the examples 
-	subdirectory in the distribution. I suggest you read them 
-	carefully so you can see how the options go together in 
-	practice. See the man page for all the options.</para>
-
-	<para>The simplest useful configuration file would be 
-	something like this:</para>
-
-	<para><programlisting>
-[global]
-	workgroup = MYGROUP
-
-[homes]
-	guest ok = no
-	read only = no
-	</programlisting></para>
+	<para>
+	There are sample configuration files in the examples subdirectory in the
+	distribution. I suggest you read them carefully so you can see how the options
+	go together in practice. See the man page for all the options.
+	</para>
+
+	<para>
+	The simplest useful configuration file would be something like this:
+	</para>
+
+	<para>
+	<programlisting>
+	[global]
+		workgroup = MYGROUP
+
+	[homes]
+		guest ok = no
+		read only = no
+	</programlisting>
+	</para>
 	
-	<para>which would allow connections by anyone with an 
-	account on the server, using either their login name or 
-	"<command>homes</command>" as the service name. (Note that I also set the 
-	workgroup that Samba is part of. See BROWSING.txt for details)</para>
+	<para>
+	This will allow connections by anyone with an account on the server, using either
+	their login name or "<command>homes</command>" as the service name.
+	(Note that the workgroup that Samba must also be set.)
+	</para>
 	
-	<para>Make sure you put the <filename>smb.conf</filename> file in the same place 
+	<para>
+	Make sure you put the <filename>smb.conf</filename> file in the same place 
 	you specified in the<filename>Makefile</filename> (the default is to 
-	look for it in <filename>/usr/local/samba/lib/</filename>).</para>
+	look for it in <filename>/usr/local/samba/lib/</filename>).
+	</para>
 
-	<para>For more information about security settings for the 
+	<para>
+	For more information about security settings for the 
 	<command>[homes]</command> share please refer to the chapter 
-	<link linkend="securing-samba">Securing Samba</link>.</para>
+	<link linkend="securing-samba">Securing Samba</link>.
+	</para>
 
 <sect3>
-	<title>Test your config file with 
-	<command>testparm</command></title>
+	<title>Test your config file with <command>testparm</command></title>
 
-	<para>It's important that you test the validity of your
-	<filename>smb.conf</filename> file using the <application>testparm</application> program. 
-	If testparm runs OK then it will list the loaded services. If 
-	not it will give an error message.</para>
+	<para>
+	It's important that you test the validity of your <filename>smb.conf</filename>
+	file using the <application>testparm</application> program. If testparm runs OK
+	then it will list the loaded services. If not it will give an error message.
+	</para>
 
-	<para>Make sure it runs OK and that the services look 
-	reasonable before proceeding. </para>
+	<para>
+	Make sure it runs OK and that the services look reasonable before proceeding.
+	</para>
 
-	<para>Always run testparm again when you change 
-	<filename>smb.conf</filename>!</para>
+	<para>
+	Always run testparm again when you change <filename>smb.conf</filename>!
+	</para>
 
 </sect3>
 </sect2>
 
-	<sect2>
+<sect2>
 	<title>SWAT</title>
 
 	<para>
@@ -99,15 +113,21 @@
 	on compiling, installing and configuring swat from source.
 	</para>
 
-	<para>To launch SWAT just run your favorite web browser and 
-	point it at "http://localhost:901/". Replace <replaceable>localhost</replaceable> with the name of the computer you are running samba on if you 
-	are running samba on a different computer than your browser.</para>
+	<para>
+	To launch SWAT just run your favorite web browser and 
+	point it at "http://localhost:901/". Replace
+	<replaceable>localhost</replaceable>
+	with the name of the computer you are running samba on if you 
+	are running samba on a different computer than your browser.
+	</para>
 
-	<para>Note that you can attach to SWAT from any IP connected 
+	<para>
+	Note that you can attach to SWAT from any IP connected 
 	machine but connecting from a remote machine leaves your 
 	connection open to password sniffing as passwords will be sent 
-	in the clear over the wire. </para>
-	</sect2>
+	in the clear over the wire. 
+	</para>
+</sect2>
 </sect1>
 
 <sect1>
@@ -179,5 +199,86 @@
 	Samba has been successfully installed at thousands of sites worldwide,
 	so maybe someone else has hit your problem and has overcome it. </para>
 
-</sect1>	
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+The following questions and issues get raised on the samba mailing list over and over again.
+</para>
+
+<sect2>
+<title>Why are so many smbd processes eating memory?</title>
+
+<para>
+Site that is running Samba on an AIX box. They are sharing out about 2 terabytes using samba.
+Samba was installed using smitty and the binaries. We seem to be experiencing a memory problem
+with this box.  When I do a svmon -Pu the monitoring program shows that smbd has several
+processes of smbd running:
+</para>
+
+<para>
+Is samba suppose to start this many different smbd processes?  Or does it run as one smbd process?  Also
+is it normal for it to be taking up this much memory?
+</para>
+
+<para>
+<programlisting>
+Inuse * 4096 = amount of memory being used by this process
+
+     Pid Command        Inuse      Pin     Pgsp  Virtual   64-bit    Mthrd
+   20950 smbd           33098     1906      181     5017        N        N
+   22262 smbd            9104     1906      5410
+   21060 smbd            9048     1906      181     5479        N        N
+   25972 smbd            8678     1906      181     5109        N        N
+   24524 smbd            8674     1906      181     5105        N        N
+   19262 smbd            8582     1906      181     5013        N        N
+   20722 smbd            8572     1906      181     5003        N        N
+   21454 smbd            8572     1906      181     5003        N        N
+   28946 smbd            8567     1906      181     4996        N        N
+   24076 smbd            8566     1906      181     4996        N        N
+   20138 smbd            8566     1906      181     4996        N        N
+   17608 smbd            8565     1906      181     4996        N        N
+   21820 smbd            8565     1906      181     4996        N        N
+   26940 smbd            8565     1906      181     4996        N        N
+   19884 smbd            8565     1906      181     4996        N        N
+    9912 smbd            8565     1906      181     4996        N        N
+   25800 smbd            8564     1906      181     4995        N        N
+   20452 smbd            8564     1906      181     4995        N        N
+   18592 smbd            8562     1906      181     4993        N        N
+   28216 smbd            8521     1906      181     4954        N        N
+   19110 smbd            8404     1906      181     4862        N        N
+
+   Total memory used:  841,592,832 bytes
+</programlisting>
+</para>
+
+
+<para>
+<emphasis>ANSWER:</emphasis> Samba consists on three core programs:
+<emphasis>nmbd, smbd, winbindd</emphasis>. <command>nmbd</command> is the name server message daemon,
+<command>smbd</command> is the server message daemon, <command>winbind</command> is the daemon that
+handles communication with Domain Controllers.
+</para>
+
+<para>
+If your system is NOT running as a WINS server, then there will be one (1) single instance of
+ <command>nmbd</command> running on your system. If it is running as a WINS server then there will be
+two (2) instances - one to handle the WINS requests.
+</para>
+
+<para>
+<command>smbd</command> handles ALL connection requests and then spawns a new process for each client
+connection made. That is why you are seeing so many of them, one (1) per client connection.
+</para>
+
+<para>
+<command>winbindd</command> will run as one or two daemons, depending on whether or not it is being
+run in "split mode" (in which case there will be two instances).
+</para>
+
+</sect2>
+</sect1>
+
 </chapter>