1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
27 >smbd -- server to provide SMB/CIFS services to clients</DIV
29 CLASS="REFSYNOPSISDIV"
37 > [-D] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P
47 >This program is part of the Samba suite.</P
52 > is the server daemon that
53 provides filesharing and printing services to Windows clients.
54 The server provides filespace and printer services to
55 clients using the SMB (or CIFS) protocol. This is compatible
56 with the LanManager protocol, and can service LanManager
57 clients. These include MSCLIENT 3.0 for DOS, Windows for
58 Workgroups, Windows 95/98/ME, Windows NT, Windows 2000,
59 OS/2, DAVE for Macintosh, and smbfs for Linux.</P
61 >An extensive description of the services that the
62 server can provide is given in the man page for the
63 configuration file controlling the attributes of those
65 HREF="smb.conf.5.html"
72 >. This man page will not describe the
73 services, but will concentrate on the administrative aspects
74 of running the server.</P
76 >Please note that there are significant security
77 implications to running this server, and the <A
78 HREF="smb.conf.5.html"
85 manpage should be regarded as mandatory reading before
86 proceeding with installation.</P
88 >A session is created whenever a client requests one.
89 Each client gets a copy of the server for each session. This
90 copy then services all connections made by the client during
91 that session. When all connections from its client are closed,
92 the copy of the server for that client terminates.</P
94 >The configuration file, and any files that it includes,
95 are automatically reloaded every minute, if they change. You
96 can force a reload by sending a SIGHUP to the server. Reloading
97 the configuration file will not affect connections to any service
98 that is already established. Either the user will have to
99 disconnect from the service, or <B
102 > killed and restarted.</P
120 >If specified, this parameter causes
121 the server to operate as a daemon. That is, it detaches
122 itself and runs in the background, fielding requests
123 on the appropriate port. Operating the server as a
124 daemon is the recommended way of running <B
128 servers that provide more than casual use file and
129 print services. This switch is assumed if <B
133 > is executed on the command line of a shell.
140 >If this parameter is specified it causes the
141 server to run "interactively", not as a daemon, even if the
142 server is executed on the command line of a shell. Setting this
143 parameter negates the implicit deamon mode when run from the
151 >Prints the help information (usage)
161 >Prints the version number for
171 >Prints information about how
175 >-d <debug level></DT
184 from 0 to 10. The default value if this parameter is
185 not specified is zero.</P
187 >The higher this value, the more detail will be
188 logged to the log files about the activities of the
189 server. At level 0, only critical errors and serious
190 warnings will be logged. Level 1 is a reasonable level for
191 day to day running - it generates a small amount of
192 information about operations carried out.</P
194 >Levels above 1 will generate considerable
195 amounts of log data, and should only be used when
196 investigating a problem. Levels above 3 are designed for
197 use only by developers and generate HUGE amounts of log
198 data, most of which is extremely cryptic.</P
200 >Note that specifying this parameter here will
202 HREF="smb.conf.5.html#loglevel"
206 > parameter in the <A
207 HREF="smb.conf.5.html"
216 >-l <log directory></DT
226 specifies a log directory into which the "log.smbd" log
227 file will be created for informational and debug
228 messages from the running server. The log
229 file generated is never removed by the server although
230 its size may be controlled by the <A
231 HREF="smb.conf.5.html#maxlogsize"
236 HREF="smb.conf.5.html"
246 If the directory specified does not exist, <B
250 will log to the default debug log location defined at compile time.
253 >The default log directory is specified at
257 >-O <socket options></DT
261 HREF="smb.conf.5.html#socketoptions"
266 HREF="smb.conf.5.html"
273 > file for details.</P
276 >-p <port number></DT
284 > is a positive integer
285 value. The default value if this parameter is not
288 >This number is the port number that will be
289 used when making connections to the server from client
290 software. The standard (well-known) port number for the
291 SMB over TCP is 139, hence the default. If you wish to
292 run the server as an ordinary user rather than
293 as root, most systems will require you to use a port
294 number greater than 1024 - ask your system administrator
295 for help if you are in this situation.</P
297 >In order for the server to be useful by most
298 clients, should you configure it on a port other
299 than 139, you will require port redirection services
300 on port 139, details of which are outlined in rfc1002.txt
303 >This parameter is not normally specified except
304 in the above situation.</P
307 >-s <configuration file></DT
310 >The file specified contains the
311 configuration details required by the server. The
312 information in this file includes server-specific
313 information such as what printcap file to use, as well
314 as descriptions of all the services that the server is
316 HREF="smb.conf.5.html"
322 > for more information.
323 The default configuration file name is determined at
348 >If the server is to be run by the
352 > meta-daemon, this file
353 must contain suitable startup information for the
354 meta-daemon. See the <A
355 HREF="UNIX_INSTALL.html"
357 >UNIX_INSTALL.html</A
359 document for details.
369 >or whatever initialization script your
372 >If running the server as a daemon at startup,
373 this file will need to contain an appropriate startup
374 sequence for the server. See the <A
375 HREF="UNIX_INSTALL.html"
377 >UNIX_INSTALL.html</A
379 document for details.</P
388 >If running the server via the
393 must contain a mapping of service name (e.g., netbios-ssn)
394 to service port (e.g., 139) and protocol type (e.g., tcp).
396 HREF="UNIX_INSTALL.html"
398 >UNIX_INSTALL.html</A
400 document for details.</P
405 >/usr/local/samba/lib/smb.conf</TT
409 >This is the default location of the
411 HREF="smb.conf.5.html"
418 server configuration file. Other common places that systems
419 install this file are <TT
421 >/usr/samba/lib/smb.conf</TT
428 >This file describes all the services the server
429 is to make available to clients. See <A
430 HREF="smb.conf.5.html"
436 > for more information.</P
452 > cannot change uid back
453 to root after a setuid() call. Such systems are called
454 trapdoor uid systems. If you have such a system,
455 you will be unable to connect from a client (such as a PC) as
456 two different users at once. Attempts to connect the
457 second user will result in access denied or
466 >ENVIRONMENT VARIABLES</H2
479 >If no printer name is specified to
480 printable services, most systems will use the value of
481 this variable (or <TT
484 > if this variable is
485 not defined) as the name of the printer to use. This
486 is not specific to the server, however.</P
499 >Samba uses PAM for authentication (when presented with a plaintext
500 password), for account checking (is this account disabled?) and for
501 session management. The degree too which samba supports PAM is restricted
502 by the limitations of the SMB protocol and the
504 HREF="smb.conf.5.html#OBEYPAMRESRICTIONS"
506 >obey pam restricions</A
508 smb.conf paramater. When this is set, the following restrictions apply:
517 >Account Validation</I
519 samba server are checked
520 against PAM to see if the account is vaild, not disabled and is permitted to
521 login at this time. This also applies to encrypted logins.
528 >Session Management</I
529 >: When not using share
530 level secuirty, users must pass PAM's session checks before access
531 is granted. Note however, that this is bypassed in share level secuirty.
532 Note also that some older pam configuration files may need a line
533 added for session support.
546 >This man page is correct for version 3.0 of
557 >Most diagnostics issued by the server are logged
558 in a specified log file. The log file name is specified
559 at compile time, but may be overridden on the command line.</P
561 >The number and nature of diagnostics available depends
562 on the debug level used by the server. If you have problems, set
563 the debug level to 3 and peruse the log files.</P
565 >Most messages are reasonably self-explanatory. Unfortunately,
566 at the time this man page was created, there are too many diagnostics
567 available in the source code to warrant describing each and every
568 diagnostic. At this stage your best bet is still to grep the
569 source code and inspect the conditions that gave rise to the
570 diagnostics you are seeing.</P
583 > a SIGHUP will cause it to
588 file within a short period of time.</P
590 >To shut down a user's <B
593 > process it is recommended
601 be used, except as a last resort, as this may leave the shared
602 memory area in an inconsistent state. The safe way to terminate
606 > is to send it a SIGTERM (-15) signal and wait for
607 it to die on its own.</P
609 >The debug log level of <B
614 HREF="smbcontrol.1.html"
621 > program (SIGUSR[1|2] signals are no longer used in
622 Samba 2.2). This is to allow transient problems to be diagnosed,
623 whilst still running at a normally low log level.</P
625 >Note that as the signal handlers send a debug write,
626 they are not re-entrant in <B
629 >. This you should wait until
633 > is in a state of waiting for an incoming SMB before
634 issuing them. It is possible to make the signal handlers safe
635 by un-blocking the signals before the select call and re-blocking
636 them after, however this would affect performance.</P
659 HREF="smb.conf.5.html"
667 HREF="smbclient.1.html"
675 HREF="testparm.1.html"
682 HREF="testprns.1.html"
688 >, and the Internet RFC's
696 In addition the CIFS (formerly SMB) specification is available
697 as a link from the Web page <A
698 HREF="http://samba.org/cifs/"
701 http://samba.org/cifs/</A
712 >The original Samba software and related utilities
713 were created by Andrew Tridgell. Samba is now developed
714 by the Samba Team as an Open Source project similar
715 to the way the Linux kernel is developed.</P
717 >The original Samba man pages were written by Karl Auer.
718 The man page sources were converted to YODL format (another
719 excellent piece of Open Source software, available at
721 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
723 > ftp://ftp.icce.rug.nl/pub/unix/</A
724 >) and updated for the Samba 2.0
725 release by Jeremy Allison. The conversion to DocBook for
726 Samba 2.2 was done by Gerald Carter</P