7 CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
27 >smbd -- server to provide SMB/CIFS services to clients</DIV
29 CLASS="REFSYNOPSISDIV"
39 > [-D] [-a] [-i] [-o] [-P] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P
49 >This program is part of the Samba suite.</P
54 > is the server daemon that
55 provides filesharing and printing services to Windows clients.
56 The server provides filespace and printer services to
57 clients using the SMB (or CIFS) protocol. This is compatible
58 with the LanManager protocol, and can service LanManager
59 clients. These include MSCLIENT 3.0 for DOS, Windows for
60 Workgroups, Windows 95/98/ME, Windows NT, Windows 2000,
61 OS/2, DAVE for Macintosh, and smbfs for Linux.</P
63 >An extensive description of the services that the
64 server can provide is given in the man page for the
65 configuration file controlling the attributes of those
67 HREF="smb.conf.5.html"
74 >. This man page will not describe the
75 services, but will concentrate on the administrative aspects
76 of running the server.</P
78 >Please note that there are significant security
79 implications to running this server, and the <A
80 HREF="smb.conf.5.html"
87 manpage should be regarded as mandatory reading before
88 proceeding with installation.</P
90 >A session is created whenever a client requests one.
91 Each client gets a copy of the server for each session. This
92 copy then services all connections made by the client during
93 that session. When all connections from its client are closed,
94 the copy of the server for that client terminates.</P
96 >The configuration file, and any files that it includes,
97 are automatically reloaded every minute, if they change. You
98 can force a reload by sending a SIGHUP to the server. Reloading
99 the configuration file will not affect connections to any service
100 that is already established. Either the user will have to
101 disconnect from the service, or <B
104 > killed and restarted.</P
122 >If specified, this parameter causes
123 the server to operate as a daemon. That is, it detaches
124 itself and runs in the background, fielding requests
125 on the appropriate port. Operating the server as a
126 daemon is the recommended way of running <B
130 servers that provide more than casual use file and
131 print services. This switch is assumed if <B
135 > is executed on the command line of a shell.
142 >If this parameter is specified, each new
143 connection will append log messages to the log file.
144 This is the default.</P
150 >If this parameter is specified it causes the
151 server to run "interactively", not as a daemon, even if the
152 server is executed on the command line of a shell. Setting this
153 parameter negates the implicit deamon mode when run from the
161 >If this parameter is specified, the
162 log files will be overwritten when opened. By default,
166 > will append entries to the log
173 >Passive option. Causes <B
177 send any network traffic out. Used for debugging by
178 the developers only.</P
184 >Prints the help information (usage)
194 >Prints the version number for
204 >Prints information about how
208 >-d <debug level></DT
217 from 0 to 10. The default value if this parameter is
218 not specified is zero.</P
220 >The higher this value, the more detail will be
221 logged to the log files about the activities of the
222 server. At level 0, only critical errors and serious
223 warnings will be logged. Level 1 is a reasonable level for
224 day to day running - it generates a small amount of
225 information about operations carried out.</P
227 >Levels above 1 will generate considerable
228 amounts of log data, and should only be used when
229 investigating a problem. Levels above 3 are designed for
230 use only by developers and generate HUGE amounts of log
231 data, most of which is extremely cryptic.</P
233 >Note that specifying this parameter here will
235 HREF="smb.conf.5.html#loglevel"
239 > parameter in the <A
240 HREF="smb.conf.5.html"
249 >-l <log directory></DT
259 specifies a log directory into which the "log.smbd" log
260 file will be created for informational and debug
261 messages from the running server. The log
262 file generated is never removed by the server although
263 its size may be controlled by the <A
264 HREF="smb.conf.5.html#maxlogsize"
269 HREF="smb.conf.5.html"
278 If the directory specified does not exist, <B
282 will log to the default debug log location defined at compile time.
285 >The default log directory is specified at
289 >-O <socket options></DT
293 HREF="smb.conf.5.html#socketoptions"
298 HREF="smb.conf.5.html"
305 > file for details.</P
308 >-p <port number></DT
316 > is a positive integer
317 value. The default value if this parameter is not
320 >This number is the port number that will be
321 used when making connections to the server from client
322 software. The standard (well-known) port number for the
323 SMB over TCP is 139, hence the default. If you wish to
324 run the server as an ordinary user rather than
325 as root, most systems will require you to use a port
326 number greater than 1024 - ask your system administrator
327 for help if you are in this situation.</P
329 >In order for the server to be useful by most
330 clients, should you configure it on a port other
331 than 139, you will require port redirection services
332 on port 139, details of which are outlined in rfc1002.txt
335 >This parameter is not normally specified except
336 in the above situation.</P
339 >-s <configuration file></DT
342 >The file specified contains the
343 configuration details required by the server. The
344 information in this file includes server-specific
345 information such as what printcap file to use, as well
346 as descriptions of all the services that the server is
348 HREF="smb.conf.5.html"
354 > for more information.
355 The default configuration file name is determined at
380 >If the server is to be run by the
384 > meta-daemon, this file
385 must contain suitable startup information for the
386 meta-daemon. See the <A
387 HREF="UNIX_INSTALL.html"
389 >UNIX_INSTALL.html</A
391 document for details.
401 >or whatever initialization script your
404 >If running the server as a daemon at startup,
405 this file will need to contain an appropriate startup
406 sequence for the server. See the <A
407 HREF="UNIX_INSTALL.html"
409 >UNIX_INSTALL.html</A
411 document for details.</P
420 >If running the server via the
425 must contain a mapping of service name (e.g., netbios-ssn)
426 to service port (e.g., 139) and protocol type (e.g., tcp).
428 HREF="UNIX_INSTALL.html"
430 >UNIX_INSTALL.html</A
432 document for details.</P
437 >/usr/local/samba/lib/smb.conf</TT
441 >This is the default location of the
443 HREF="smb.conf.5.html"
450 server configuration file. Other common places that systems
451 install this file are <TT
453 >/usr/samba/lib/smb.conf</TT
460 >This file describes all the services the server
461 is to make available to clients. See <A
462 HREF="smb.conf.5.html"
468 > for more information.</P
484 > cannot change uid back
485 to root after a setuid() call. Such systems are called
486 trapdoor uid systems. If you have such a system,
487 you will be unable to connect from a client (such as a PC) as
488 two different users at once. Attempts to connect the
489 second user will result in access denied or
498 >ENVIRONMENT VARIABLES</H2
511 >If no printer name is specified to
512 printable services, most systems will use the value of
513 this variable (or <TT
516 > if this variable is
517 not defined) as the name of the printer to use. This
518 is not specific to the server, however.</P
531 >Samba uses PAM for authentication (when presented with a plaintext
532 password), for account checking (is this account disabled?) and for
533 session management. The degree too which samba supports PAM is restricted
534 by the limitations of the SMB protocol and the
536 HREF="smb.conf.5.html#OBEYPAMRESRICTIONS"
538 >obey pam restricions</A
540 smb.conf paramater. When this is set, the following restrictions apply:
548 >Account Validation</EM
549 >: All acccesses to a
550 samba server are checked
551 against PAM to see if the account is vaild, not disabled and is permitted to
552 login at this time. This also applies to encrypted logins.
558 >Session Management</EM
559 >: When not using share
560 level secuirty, users must pass PAM's session checks before access
561 is granted. Note however, that this is bypassed in share level secuirty.
562 Note also that some older pam configuration files may need a line
563 added for session support.
576 >This man page is correct for version 2.2 of
587 >Most diagnostics issued by the server are logged
588 in a specified log file. The log file name is specified
589 at compile time, but may be overridden on the command line.</P
591 >The number and nature of diagnostics available depends
592 on the debug level used by the server. If you have problems, set
593 the debug level to 3 and peruse the log files.</P
595 >Most messages are reasonably self-explanatory. Unfortunately,
596 at the time this man page was created, there are too many diagnostics
597 available in the source code to warrant describing each and every
598 diagnostic. At this stage your best bet is still to grep the
599 source code and inspect the conditions that gave rise to the
600 diagnostics you are seeing.</P
613 > a SIGHUP will cause it to
618 file within a short period of time.</P
620 >To shut down a user's <B
623 > process it is recommended
630 be used, except as a last resort, as this may leave the shared
631 memory area in an inconsistent state. The safe way to terminate
635 > is to send it a SIGTERM (-15) signal and wait for
636 it to die on its own.</P
638 >The debug log level of <B
643 HREF="smbcontrol.1.html"
650 > program (SIGUSR[1|2] signals are no longer used in
651 Samba 2.2). This is to allow transient problems to be diagnosed,
652 whilst still running at a normally low log level.</P
654 >Note that as the signal handlers send a debug write,
655 they are not re-entrant in <B
658 >. This you should wait until
662 > is in a state of waiting for an incoming SMB before
663 issuing them. It is possible to make the signal handlers safe
664 by un-blocking the signals before the select call and re-blocking
665 them after, however this would affect performance.</P
688 HREF="smb.conf.5.html"
696 HREF="smbclient.1.html"
704 HREF="testparm.1.html"
711 HREF="testprns.1.html"
717 >, and the Internet RFC's
725 In addition the CIFS (formerly SMB) specification is available
726 as a link from the Web page <A
727 HREF="http://samba.org/cifs/"
730 http://samba.org/cifs/</A
741 >The original Samba software and related utilities
742 were created by Andrew Tridgell. Samba is now developed
743 by the Samba Team as an Open Source project similar
744 to the way the Linux kernel is developed.</P
746 >The original Samba man pages were written by Karl Auer.
747 The man page sources were converted to YODL format (another
748 excellent piece of Open Source software, available at
750 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
752 > ftp://ftp.icce.rug.nl/pub/unix/</A
753 >) and updated for the Samba 2.0
754 release by Jeremy Allison. The conversion to DocBook for
755 Samba 2.2 was done by Gerald Carter</P