From 3bb3f2d0ce1165d0cac683f507d838d20c8c743b Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Sat, 14 Nov 1998 03:01:40 +0000 Subject: Update for 2.0beta1. Jeremy. (This used to be commit 598d0255d40da29ebab3d1a3c9eb66ba654db7b5) --- docs/htmldocs/smbd.8.html | 67 +++++++++++++++++++++++++---------------------- 1 file changed, 36 insertions(+), 31 deletions(-) (limited to 'docs/htmldocs/smbd.8.html') diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index cd00af3b27..a6e0f32e12 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -3,7 +3,7 @@ -smbd +smbd (8) @@ -11,7 +11,7 @@
-

smbd

+

smbd (8)

Samba

23 Oct 1998

@@ -29,7 +29,8 @@

DESCRIPTION


This program is part of the Samba suite. -


smbd is the server daemon that provides filesharing services to +


smbd is the server daemon that provides filesharing and printing +services to Windows clients. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. This is compatible with the LanManager protocol, and can service LanManager clients. These @@ -37,16 +38,18 @@ include MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows 95, Windows NT, OS/2, DAVE for Macintosh, and smbfs for Linux.


An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the -attributes of those services (see smb.conf (5)). This man page +attributes of those services (see +smb.conf (5). This man page will not describe the services, but will concentrate on the administrative aspects of running the server.


Please note that there are significant security implications to -running this server, and the smb.conf (5) manpage should be +running this server, and the +smb.conf (5) manpage should be regarded as mandatory reading before proceeding with installation.


A session is created whenever a client requests one. Each client gets a copy of the server for each session. This copy then services all connections made by the client during that session. When all -connections from its client are are closed, the copy of the server for +connections from its client are closed, the copy of the server for that client terminates.


The configuration file, and any files that it includes, are automatically reloaded every minute, if they change. You can force a @@ -116,13 +119,13 @@ rfc1002.txt section 4.3.5.


This parameter is not normally specified except in the above situation.


-

  • -s configuration file The default configuration file name is -determined at compile time. -


    The file specified contains the configuration details required by the +

  • -s configuration file +The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See smb.conf (5) for more information. +The default configuration file name is determined at compile time.


  • -i scope This specifies a NetBIOS scope that the server will use to communicate with when generating NetBIOS names. For details on the @@ -142,23 +145,23 @@ out. Used for debugging by the developers only.


    /etc/inetd.conf


    If the server is to be run by the inetd meta-daemon, this file must contain suitable startup information for the meta-daemon. See the -section INSTALLATION below. +section INSTALLATION below.


    /etc/rc -


    (or whatever initialisation script your system uses). +


    (or whatever initialization script your system uses).


    If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. See the -section INSTALLATION below. +section INSTALLATION below.


    /etc/services


    If running the server via the meta-daemon inetd, this file must -contain a mapping of service name (eg., netbios-ssn) to service port -(eg., 139) and protocol type (eg., tcp). See the section -INSTALLATION below. +contain a mapping of service name (e.g., netbios-ssn) to service port +(e.g., 139) and protocol type (e.g., tcp). See the section +INSTALLATION below.


    /usr/local/samba/lib/smb.conf


    This is the default location of the smb.conf server configuration file. Other common places that systems install this file are /usr/samba/lib/smb.conf and /etc/smb.conf.


    This file describes all the services the server is to make available -to clients. See smb.conf (5) for more information. +to clients. See smb.conf (5) for more information.


    LIMITATIONS

    @@ -196,10 +199,10 @@ at the time this was written. It is possible that this hole only exists in Linux, as testing on other systems has thus far shown them to be immune.


    The server log files should be put in a directory readable and -writable only by root, as the log files may contain sensitive +writeable only by root, as the log files may contain sensitive information.


    The configuration file should be placed in a directory readable and -writable only by root, as the configuration file controls security for +writeable only by root, as the configuration file controls security for the services offered by the server. The configuration file can be made readable by all if desired, but this is not necessary for correct operation of the server and is not recommended. A sample configuration @@ -218,8 +221,9 @@ faster. If run from a meta-daemon some memory will be saved and utilities such as the tcpd TCP-wrapper may be used for extra security. For serious use as file server it is recommended that smbd be run as a daemon. -


    When you've decided, continue with either RUNNING THE SERVER AS A -DAEMON or RUNNING THE SERVER ON REQUEST. +


    When you've decided, continue with either +RUNNING THE SERVER AS A DAEMON or +RUNNING THE SERVER ON REQUEST.


    RUNNING THE SERVER AS A DAEMON

    @@ -239,17 +243,17 @@ files. Wherever appropriate (for example, in /etc/rc), insert the following line, substituting port number, log file location, configuration file location and debug level as desired:


    /usr/local/samba/bin/smbd -D -l /var/adm/smblogs/log -s /usr/local/samba/lib/smb.conf -


    (The above should appear in your initialisation script as a single line. +


    (The above should appear in your initialization script as a single line. Depending on your terminal characteristics, it may not appear that way in this man page. If the above appears as more than one line, please treat any newlines or indentation as a single space or TAB character.)


    If the options used at compile time are appropriate for your system, -all parameters except the desired debug level and -D may be -omitted. See the section OPTIONS above. +all parameters except -D may be +omitted. See the section OPTIONS above.


    RUNNING THE SERVER ON REQUEST

    -


    If your system uses a meta-daemon such as inetd, you can arrange to +


    If your system uses a meta-daemon such as inetd, you can arrange to have the smbd server started whenever a process attempts to connect to it. This requires several changes to the startup files on the host machine. If you are experimenting as an ordinary user rather than as @@ -284,10 +288,10 @@ start with, the following two services should be all you need: [homes] - writable = yes + writeable = yes [printers] - writable = no + writeable = no printable = yes path = /tmp public = yes @@ -307,7 +311,8 @@ tables if they receive a HUP signal.


    If your machine's name is "fred" and your name is "mary", you should now be able to connect to the service \\fred\mary.


    To properly test and experiment with the server, we recommend using -the smbclient program (see smbclient (1)) and also going through +the smbclient program (see +smbclient (1)) and also going through the steps outlined in the file DIAGNOSIS.txt in the docs/ directory of your Samba installation.


    @@ -323,8 +328,8 @@ overridden on the command line.


    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. -


    Most messages are reasonably self-explanatory. Unfortunately, at time -of creation of this man page there are too many diagnostics available +


    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. @@ -335,7 +340,7 @@ the conditions that gave rise to the diagnostics you are seeing. configuration file within a short period of time.


    To shut down a users smbd process it is recommended that SIGKILL (-9) NOT be used, except as a last resort, as this may leave the shared -memory area in an inconsistant state. The safe way to terminate an +memory area in an inconsistent state. The safe way to terminate an smbd is to send it a SIGTERM (-15) signal and wait for it to die on its own.


    The debug log level of smbd may be raised @@ -363,7 +368,7 @@ specification is available as a link from the Web page :

    AUTHOR


    The original Samba software and related utilities were created by -Andrew Tridgell (samba-bugs@samba.anu.edu.au). Samba is now developed +Andrew Tridgell samba-bugs@samba.anu.edu.au. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.


    The original Samba man pages were written by Karl Auer. The man page -- cgit