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 >The default log directory is specified at
282 >-O <socket options></DT
286 HREF="smb.conf.5.html#socketoptions"
291 HREF="smb.conf.5.html"
298 > file for details.</P
301 >-p <port number></DT
309 > is a positive integer
310 value. The default value if this parameter is not
313 >This number is the port number that will be
314 used when making connections to the server from client
315 software. The standard (well-known) port number for the
316 SMB over TCP is 139, hence the default. If you wish to
317 run the server as an ordinary user rather than
318 as root, most systems will require you to use a port
319 number greater than 1024 - ask your system administrator
320 for help if you are in this situation.</P
322 >In order for the server to be useful by most
323 clients, should you configure it on a port other
324 than 139, you will require port redirection services
325 on port 139, details of which are outlined in rfc1002.txt
328 >This parameter is not normally specified except
329 in the above situation.</P
332 >-s <configuration file></DT
335 >The file specified contains the
336 configuration details required by the server. The
337 information in this file includes server-specific
338 information such as what printcap file to use, as well
339 as descriptions of all the services that the server is
341 HREF="smb.conf.5.html"
347 > for more information.
348 The default configuration file name is determined at
373 >If the server is to be run by the
377 > meta-daemon, this file
378 must contain suitable startup information for the
379 meta-daemon. See the <A
380 HREF="UNIX_INSTALL.html"
382 >UNIX_INSTALL.html</A
384 document for details.
394 >or whatever initialization script your
397 >If running the server as a daemon at startup,
398 this file will need to contain an appropriate startup
399 sequence for the server. See the <A
400 HREF="UNIX_INSTALL.html"
402 >UNIX_INSTALL.html</A
404 document for details.</P
413 >If running the server via the
418 must contain a mapping of service name (e.g., netbios-ssn)
419 to service port (e.g., 139) and protocol type (e.g., tcp).
421 HREF="UNIX_INSTALL.html"
423 >UNIX_INSTALL.html</A
425 document for details.</P
430 >/usr/local/samba/lib/smb.conf</TT
434 >This is the default location of the
436 HREF="smb.conf.5.html"
443 server configuration file. Other common places that systems
444 install this file are <TT
446 >/usr/samba/lib/smb.conf</TT
453 >This file describes all the services the server
454 is to make available to clients. See <A
455 HREF="smb.conf.5.html"
461 > for more information.</P
477 > cannot change uid back
478 to root after a setuid() call. Such systems are called
479 trapdoor uid systems. If you have such a system,
480 you will be unable to connect from a client (such as a PC) as
481 two different users at once. Attempts to connect the
482 second user will result in access denied or
491 >ENVIRONMENT VARIABLES</H2
504 >If no printer name is specified to
505 printable services, most systems will use the value of
506 this variable (or <TT
509 > if this variable is
510 not defined) as the name of the printer to use. This
511 is not specific to the server, however.</P
524 >Samba uses PAM for authentication (when presented with a plaintext
525 password), for account checking (is this account disabled?) and for
526 session management. The degree too which samba supports PAM is restricted
527 by the limitations of the SMB protocol and the
529 HREF="smb.conf.5.html#OBEYPAMRESRICTIONS"
531 >obey pam restricions</A
533 smb.conf paramater. When this is set, the following restrictions apply:
541 >Account Validation</EM
542 >: All acccesses to a
543 samba server are checked
544 against PAM to see if the account is vaild, not disabled and is permitted to
545 login at this time. This also applies to encrypted logins.
551 >Session Management</EM
552 >: When not using share
553 level secuirty, users must pass PAM's session checks before access
554 is granted. Note however, that this is bypassed in share level secuirty.
555 Note also that some older pam configuration files may need a line
556 added for session support.
569 >This man page is correct for version 2.2 of
580 >Most diagnostics issued by the server are logged
581 in a specified log file. The log file name is specified
582 at compile time, but may be overridden on the command line.</P
584 >The number and nature of diagnostics available depends
585 on the debug level used by the server. If you have problems, set
586 the debug level to 3 and peruse the log files.</P
588 >Most messages are reasonably self-explanatory. Unfortunately,
589 at the time this man page was created, there are too many diagnostics
590 available in the source code to warrant describing each and every
591 diagnostic. At this stage your best bet is still to grep the
592 source code and inspect the conditions that gave rise to the
593 diagnostics you are seeing.</P
606 > a SIGHUP will cause it to
611 file within a short period of time.</P
613 >To shut down a user's <B
616 > process it is recommended
623 be used, except as a last resort, as this may leave the shared
624 memory area in an inconsistent state. The safe way to terminate
628 > is to send it a SIGTERM (-15) signal and wait for
629 it to die on its own.</P
631 >The debug log level of <B
636 HREF="smbcontrol.1.html"
643 > program (SIGUSR[1|2] signals are no longer used in
644 Samba 2.2). This is to allow transient problems to be diagnosed,
645 whilst still running at a normally low log level.</P
647 >Note that as the signal handlers send a debug write,
648 they are not re-entrant in <B
651 >. This you should wait until
655 > is in a state of waiting for an incoming SMB before
656 issuing them. It is possible to make the signal handlers safe
657 by un-blocking the signals before the select call and re-blocking
658 them after, however this would affect performance.</P
681 HREF="smb.conf.5.html"
689 HREF="smbclient.1.html"
697 HREF="testparm.1.html"
704 HREF="testprns.1.html"
710 >, and the Internet RFC's
718 In addition the CIFS (formerly SMB) specification is available
719 as a link from the Web page <A
720 HREF="http://samba.org/cifs/"
723 http://samba.org/cifs/</A
734 >The original Samba software and related utilities
735 were created by Andrew Tridgell. Samba is now developed
736 by the Samba Team as an Open Source project similar
737 to the way the Linux kernel is developed.</P
739 >The original Samba man pages were written by Karl Auer.
740 The man page sources were converted to YODL format (another
741 excellent piece of Open Source software, available at
743 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
745 > ftp://ftp.icce.rug.nl/pub/unix/</A
746 >) and updated for the Samba 2.0
747 release by Jeremy Allison. The conversion to DocBook for
748 Samba 2.2 was done by Gerald Carter</P