diff options
Diffstat (limited to 'docs/htmldocs/smbd.8.html')
| -rw-r--r-- | docs/htmldocs/smbd.8.html | 126 |
1 files changed, 64 insertions, 62 deletions
diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 6a4996d9387..e1ea92b986a 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -36,12 +36,12 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbd</B -> [-D] [-a] [-i] [-o] [-P] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P +> [-D] [-a] [-i] [-o] [-P] [-h] [-V] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN24" +NAME="AEN23" ></A ><H2 >DESCRIPTION</H2 @@ -84,7 +84,7 @@ CLASS="FILENAME" >smb.conf(5)</TT ></A > - manpage should be regarded as mandatory reading before + manpage should be regarded as mandatory reading before proceeding with installation.</P ><P >A session is created whenever a client requests one. @@ -106,7 +106,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN38" +NAME="AEN37" ></A ><H2 >OPTIONS</H2 @@ -198,13 +198,6 @@ CLASS="COMMAND" >.</P ></DD ><DT ->-b</DT -><DD -><P ->Prints information about how - Samba was built.</P -></DD -><DT >-d <debug level></DT ><DD ><P @@ -221,7 +214,7 @@ CLASS="REPLACEABLE" logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for - day to day running - it generates a small amount of + day to day running - it generates a small amount of information about operations carried out.</P ><P >Levels above 1 will generate considerable @@ -313,14 +306,14 @@ CLASS="REPLACEABLE" ><I >port number</I ></TT -> is a positive integer +> is a positive integer value. The default value if this parameter is not specified is 139.</P ><P >This number is the port number that will be used when making connections to the server from client software. The standard (well-known) port number for the - SMB over TCP is 139, hence the default. If you wish to + SMB over TCP is 139, hence the default. If you wish to run the server as an ordinary user rather than as root, most systems will require you to use a port number greater than 1024 - ask your system administrator @@ -352,7 +345,7 @@ CLASS="FILENAME" > smb.conf(5)</TT ></A > for more information. - The default configuration file name is determined at + The default configuration file name is determined at compile time.</P ></DD ></DL @@ -361,7 +354,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN122" +NAME="AEN117" ></A ><H2 >FILES</H2 @@ -377,7 +370,7 @@ CLASS="FILENAME" ></DT ><DD ><P ->If the server is to be run by the +>If the server is to be run by the <B CLASS="COMMAND" >inetd</B @@ -398,11 +391,11 @@ CLASS="FILENAME" ></DT ><DD ><P ->or whatever initialization script your +>or whatever initialization script your system uses).</P ><P ->If running the server as a daemon at startup, - this file will need to contain an appropriate startup +>If running the server as a daemon at startup, + this file will need to contain an appropriate startup sequence for the server. See the <A HREF="UNIX_INSTALL.html" TARGET="_top" @@ -417,13 +410,13 @@ CLASS="FILENAME" ></DT ><DD ><P ->If running the server via the +>If running the server via the meta-daemon <B CLASS="COMMAND" >inetd</B ->, this file - must contain a mapping of service name (e.g., netbios-ssn) - to service port (e.g., 139) and protocol type (e.g., tcp). +>, this file + must contain a mapping of service name (e.g., netbios-ssn) + to service port (e.g., 139) and protocol type (e.g., tcp). See the <A HREF="UNIX_INSTALL.html" TARGET="_top" @@ -438,7 +431,7 @@ CLASS="FILENAME" ></DT ><DD ><P ->This is the default location of the +>This is the default location of the <A HREF="smb.conf.5.html" TARGET="_top" @@ -447,17 +440,17 @@ CLASS="FILENAME" >smb.conf</TT ></A > - server configuration file. Other common places that systems + server configuration file. Other common places that systems install this file are <TT CLASS="FILENAME" >/usr/samba/lib/smb.conf</TT -> +> and <TT CLASS="FILENAME" >/etc/smb.conf</TT >.</P ><P ->This file describes all the services the server +>This file describes all the services the server is to make available to clients. See <A HREF="smb.conf.5.html" TARGET="_top" @@ -473,7 +466,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN158" +NAME="AEN153" ></A ><H2 >LIMITATIONS</H2 @@ -481,10 +474,10 @@ NAME="AEN158" >On some systems <B CLASS="COMMAND" >smbd</B -> cannot change uid back - to root after a setuid() call. Such systems are called - trapdoor uid systems. If you have such a system, - you will be unable to connect from a client (such as a PC) as +> cannot change uid back + to root after a setuid() call. Such systems are called + trapdoor uid systems. If you have such a system, + you will be unable to connect from a client (such as a PC) as two different users at once. Attempts to connect the second user will result in access denied or similar.</P @@ -492,7 +485,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN162" +NAME="AEN157" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -523,15 +516,15 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN171" +NAME="AEN166" ></A ><H2 >PAM INTERACTION</H2 ><P ->Samba uses PAM for authentication (when presented with a plaintext +>Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management. The degree too which samba supports PAM is restricted - by the limitations of the SMB protocol and the + by the limitations of the SMB protocol and the <A HREF="smb.conf.5.html#OBEYPAMRESRICTIONS" TARGET="_top" @@ -557,7 +550,7 @@ TARGET="_top" ><EM >Session Management</EM >: When not using share - level secuirty, users must pass PAM's session checks before access + level secuirty, users must pass PAM's session checks before access is granted. Note however, that this is bypassed in share level secuirty. Note also that some older pam configuration files may need a line added for session support. @@ -568,41 +561,50 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN182" +NAME="AEN177" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of +>This man page is correct for version 2.2 of the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN185" +NAME="AEN180" ></A ><H2 ->DIAGNOSTICS</H2 -><P ->Most diagnostics issued by the server are logged - in a specified log file. The log file name is specified +>TROUBLESHOOTING</H2 +><P +> One of the common causes of difficulty when installing Samba and SWAT + is the existsnece of some type of firewall or port filtering software + on the Samba server. Make sure that the appropriate ports + outlined in this man page are available on the server and are not currently + being blocked by some type of security software such as iptables or + "port sentry". For more troubleshooting information, refer to the additional + documentation included in the Samba distribution. + </P +><P +>Most diagnostics issued by the server are logged + in a specified log file. The log file name is specified at compile time, but may be overridden on the command line.</P ><P ->The number and nature of diagnostics available depends - on the debug level used by the server. If you have problems, set +>The number and nature of diagnostics available depends + on the debug level used by the server. If you have problems, set the debug level to 3 and peruse the log files.</P ><P ->Most messages are reasonably self-explanatory. Unfortunately, - at the time this man page was created, there are too many diagnostics - available in the source code to warrant describing each and every - diagnostic. At this stage your best bet is still to grep the - source code and inspect the conditions that gave rise to the +>Most messages are reasonably self-explanatory. Unfortunately, + at the time this man page was created, there are too many diagnostics + available in the source code to warrant describing each and every + diagnostic. At this stage your best bet is still to grep the + source code and inspect the conditions that gave rise to the diagnostics you are seeing.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN190" +NAME="AEN186" ></A ><H2 >SIGNALS</H2 @@ -610,29 +612,29 @@ NAME="AEN190" >Sending the <B CLASS="COMMAND" >smbd</B -> a SIGHUP will cause it to +> a SIGHUP will cause it to reload its <TT CLASS="FILENAME" >smb.conf</TT -> configuration +> configuration file within a short period of time.</P ><P >To shut down a user's <B CLASS="COMMAND" >smbd</B -> process it is recommended +> process it is recommended that <B CLASS="COMMAND" >SIGKILL (-9)</B > <EM >NOT</EM -> +> be used, except as a last resort, as this may leave the shared - memory area in an inconsistent state. The safe way to terminate + memory area in an inconsistent state. The safe way to terminate an <B CLASS="COMMAND" >smbd</B -> is to send it a SIGTERM (-15) signal and wait for +> is to send it a SIGTERM (-15) signal and wait for it to die on its own.</P ><P >The debug log level of <B @@ -648,7 +650,7 @@ CLASS="COMMAND" </B ></A > program (SIGUSR[1|2] signals are no longer used in - Samba 2.2). This is to allow transient problems to be diagnosed, + Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running at a normally low log level.</P ><P >Note that as the signal handlers send a debug write, @@ -667,7 +669,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN207" +NAME="AEN203" ></A ><H2 >SEE ALSO</H2 @@ -733,7 +735,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN224" +NAME="AEN220" ></A ><H2 >AUTHOR</H2 |