1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbd — server to provide SMB/CIFS services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">smbd</code> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number(s)>] [-O <socket option>] [-s <configuration file>]</p></div></div><div class="refsect1" lang="en"><a name="id2450634"></a><h2>DESCRIPTION</h2><p>This program is part of the <a href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><span><strong class="command">smbd</strong></span> is the server daemon that
2 provides filesharing and printing services to Windows clients.
3 The server provides filespace and printer services to
4 clients using the SMB (or CIFS) protocol. This is compatible
5 with the LanManager protocol, and can service LanManager
6 clients. These include MSCLIENT 3.0 for DOS, Windows for
7 Workgroups, Windows 95/98/ME, Windows NT, Windows 2000,
8 OS/2, DAVE for Macintosh, and smbfs for Linux.</p><p>An extensive description of the services that the
9 server can provide is given in the man page for the
10 configuration file controlling the attributes of those
11 services (see <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>. This man page will not describe the
12 services, but will concentrate on the administrative aspects
13 of running the server.</p><p>Please note that there are significant security
14 implications to running this server, and the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> manual page should be regarded as mandatory reading before
15 proceeding with installation.</p><p>A session is created whenever a client requests one.
16 Each client gets a copy of the server for each session. This
17 copy then services all connections made by the client during
18 that session. When all connections from its client are closed,
19 the copy of the server for that client terminates.</p><p>The configuration file, and any files that it includes,
20 are automatically reloaded every minute, if they change. You
21 can force a reload by sending a SIGHUP to the server. Reloading
22 the configuration file will not affect connections to any service
23 that is already established. Either the user will have to
24 disconnect from the service, or <span><strong class="command">smbd</strong></span> killed and restarted.</p></div><div class="refsect1" lang="en"><a name="id2450722"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes
25 the server to operate as a daemon. That is, it detaches
26 itself and runs in the background, fielding requests
27 on the appropriate port. Operating the server as a
28 daemon is the recommended way of running <span><strong class="command">smbd</strong></span> for
29 servers that provide more than casual use file and
30 print services. This switch is assumed if <span><strong class="command">smbd
31 </strong></span> is executed on the command line of a shell.
32 </p></dd><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
33 the main <span><strong class="command">smbd</strong></span> process to not daemonize,
34 i.e. double-fork and disassociate with the terminal.
35 Child processes are still created as normal to service
36 each connection request, but the main process does not
37 exit. This operation mode is suitable for running
38 <span><strong class="command">smbd</strong></span> under process supervisors such
39 as <span><strong class="command">supervise</strong></span> and <span><strong class="command">svscan</strong></span>
40 from Daniel J. Bernstein's <span><strong class="command">daemontools</strong></span>
41 package, or the AIX process monitor.
42 </p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
43 <span><strong class="command">smbd</strong></span> to log to standard output rather
44 than a file.</p></dd><dt><span class="term">-i</span></dt><dd><p>If this parameter is specified it causes the
45 server to run "interactively", not as a daemon, even if the
46 server is executed on the command line of a shell. Setting this
47 parameter negates the implicit deamon mode when run from the
48 command line. <span><strong class="command">smbd</strong></span> also logs to standard
49 output, as if the <span><strong class="command">-S</strong></span> parameter had been
51 </p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the program version number.
52 </p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the
53 configuration details required by the server. The
54 information in this file includes server-specific
55 information such as what printcap file to use, as well
56 as descriptions of all the services that the server is
57 to provide. See <code class="filename">smb.conf</code> for more information.
58 The default configuration file name is determined at
59 compile time.</p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer
60 from 0 to 10. The default value if this parameter is
61 not specified is zero.</p><p>The higher this value, the more detail will be
62 logged to the log files about the activities of the
63 server. At level 0, only critical errors and serious
64 warnings will be logged. Level 1 is a reasonable level for
65 day-to-day running - it generates a small amount of
66 information about operations carried out.</p><p>Levels above 1 will generate considerable
67 amounts of log data, and should only be used when
68 investigating a problem. Levels above 3 are designed for
69 use only by developers and generate HUGE amounts of log
70 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
71 override the <a class="indexterm" name="id2450987"></a> parameter
72 in the <code class="filename">smb.conf</code> file.</p></dd><dt><span class="term">-l|--logfile=logdirectory</span></dt><dd><p>Base directory name for log/debug files. The extension
73 <code class="constant">".progname"</code> will be appended (e.g. log.smbclient,
74 log.smbd, etc...). The log file is never removed by the client.
75 </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
76 </p></dd><dt><span class="term">-b</span></dt><dd><p>Prints information about how
77 Samba was built.</p></dd><dt><span class="term">-p <port number(s)></span></dt><dd><p><em class="replaceable"><code>port number(s)</code></em> is a
78 space or comma-separated list of TCP ports smbd should listen on.
79 The default value is taken from the <a class="indexterm" name="id2451057"></a>ports parameter in <code class="filename">smb.conf</code></p><p>The default ports are 139 (used for SMB over NetBIOS over TCP)
80 and port 445 (used for plain SMB over TCP).
81 </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2451078"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/inetd.conf</code></span></dt><dd><p>If the server is to be run by the
82 <span><strong class="command">inetd</strong></span> meta-daemon, this file
83 must contain suitable startup information for the
85 </p></dd><dt><span class="term"><code class="filename">/etc/rc</code></span></dt><dd><p>or whatever initialization script your
86 system uses).</p><p>If running the server as a daemon at startup,
87 this file will need to contain an appropriate startup
88 sequence for the server. </p></dd><dt><span class="term"><code class="filename">/etc/services</code></span></dt><dd><p>If running the server via the
89 meta-daemon <span><strong class="command">inetd</strong></span>, this file
90 must contain a mapping of service name (e.g., netbios-ssn)
91 to service port (e.g., 139) and protocol type (e.g., tcp).
92 </p></dd><dt><span class="term"><code class="filename">/usr/local/samba/lib/smb.conf</code></span></dt><dd><p>This is the default location of the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> server configuration file. Other common places that systems
93 install this file are <code class="filename">/usr/samba/lib/smb.conf</code>
94 and <code class="filename">/etc/samba/smb.conf</code>.</p><p>This file describes all the services the server
95 is to make available to clients. See <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> for more information.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2451421"></a><h2>LIMITATIONS</h2><p>On some systems <span><strong class="command">smbd</strong></span> cannot change uid back
96 to root after a setuid() call. Such systems are called
97 trapdoor uid systems. If you have such a system,
98 you will be unable to connect from a client (such as a PC) as
99 two different users at once. Attempts to connect the
100 second user will result in access denied or
101 similar.</p></div><div class="refsect1" lang="en"><a name="id2451442"></a><h2>ENVIRONMENT VARIABLES</h2><div class="variablelist"><dl><dt><span class="term"><code class="envar">PRINTER</code></span></dt><dd><p>If no printer name is specified to
102 printable services, most systems will use the value of
103 this variable (or <code class="constant">lp</code> if this variable is
104 not defined) as the name of the printer to use. This
105 is not specific to the server, however.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2451472"></a><h2>PAM INTERACTION</h2><p>Samba uses PAM for authentication (when presented with a plaintext
106 password), for account checking (is this account disabled?) and for
107 session management. The degree too which samba supports PAM is restricted
108 by the limitations of the SMB protocol and the <a class="indexterm" name="id2451484"></a>obey pam restrictions <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> paramater. When this is set, the following restrictions apply:
109 </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Account Validation</em></span>: All accesses to a
110 samba server are checked
111 against PAM to see if the account is vaild, not disabled and is permitted to
112 login at this time. This also applies to encrypted logins.
113 </p></li><li><p><span class="emphasis"><em>Session Management</em></span>: When not using share
114 level secuirty, users must pass PAM's session checks before access
115 is granted. Note however, that this is bypassed in share level secuirty.
116 Note also that some older pam configuration files may need a line
117 added for session support.
118 </p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2451528"></a><h2>VERSION</h2><p>This man page is correct for version 3.0 of
119 the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2451539"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the server are logged
120 in a specified log file. The log file name is specified
121 at compile time, but may be overridden on the command line.</p><p>The number and nature of diagnostics available depends
122 on the debug level used by the server. If you have problems, set
123 the debug level to 3 and peruse the log files.</p><p>Most messages are reasonably self-explanatory. Unfortunately,
124 at the time this man page was created, there are too many diagnostics
125 available in the source code to warrant describing each and every
126 diagnostic. At this stage your best bet is still to grep the
127 source code and inspect the conditions that gave rise to the
128 diagnostics you are seeing.</p></div><div class="refsect1" lang="en"><a name="id2451567"></a><h2>TDB FILES</h2><p>Samba stores it's data in several TDB (Trivial Database) files, usually located in <code class="filename">/var/lib/samba</code>.</p><p>
129 (*) information persistent across restarts (but not
130 necessarily important to backup).
131 </p><div class="variablelist"><dl><dt><span class="term">account_policy.tdb*</span></dt><dd><p>NT account policy settings such as pw expiration, etc...</p></dd><dt><span class="term">brlock.tdb</span></dt><dd><p>byte range locks</p></dd><dt><span class="term">browse.dat</span></dt><dd><p>browse lists</p></dd><dt><span class="term">connections.tdb</span></dt><dd><p>share connections (used to enforce max connections, etc...)</p></dd><dt><span class="term">gencache.tdb</span></dt><dd><p>generic caching db</p></dd><dt><span class="term">group_mapping.tdb*</span></dt><dd><p>group mapping information</p></dd><dt><span class="term">locking.tdb</span></dt><dd><p>share modes & oplocks</p></dd><dt><span class="term">login_cache.tdb*</span></dt><dd><p>bad pw attempts</p></dd><dt><span class="term">messages.tdb</span></dt><dd><p>Samba messaging system</p></dd><dt><span class="term">netsamlogon_cache.tdb*</span></dt><dd><p>cache of user net_info_3 struct from net_samlogon() request (as a domain member)</p></dd><dt><span class="term">ntdrivers.tdb*</span></dt><dd><p>installed printer drivers</p></dd><dt><span class="term">ntforms.tdb*</span></dt><dd><p>installed printer forms</p></dd><dt><span class="term">ntprinters.tdb*</span></dt><dd><p>installed printer information</p></dd><dt><span class="term">printing/</span></dt><dd><p>directory containing tdb per print queue of cached lpq output</p></dd><dt><span class="term">registry.tdb</span></dt><dd><p>Windows registry skeleton (connect via regedit.exe)</p></dd><dt><span class="term">sessionid.tdb</span></dt><dd><p>session information (e.g. support for 'utmp = yes')</p></dd><dt><span class="term">share_info.tdb*</span></dt><dd><p>share acls</p></dd><dt><span class="term">winbindd_cache.tdb</span></dt><dd><p>winbindd's cache of user lists, etc...</p></dd><dt><span class="term">winbindd_idmap.tdb*</span></dt><dd><p>winbindd's local idmap db</p></dd><dt><span class="term">wins.dat*</span></dt><dd><p>wins database when 'wins support = yes'</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2498442"></a><h2>SIGNALS</h2><p>Sending the <span><strong class="command">smbd</strong></span> a SIGHUP will cause it to
132 reload its <code class="filename">smb.conf</code> configuration
133 file within a short period of time.</p><p>To shut down a user's <span><strong class="command">smbd</strong></span> process it is recommended
134 that <span><strong class="command">SIGKILL (-9)</strong></span> <span class="emphasis"><em>NOT</em></span>
135 be used, except as a last resort, as this may leave the shared
136 memory area in an inconsistent state. The safe way to terminate
137 an <span><strong class="command">smbd</strong></span> is to send it a SIGTERM (-15) signal and wait for
138 it to die on its own.</p><p>The debug log level of <span><strong class="command">smbd</strong></span> may be raised
139 or lowered using <a href="smbcontrol.1.html"><span class="citerefentry"><span class="refentrytitle">smbcontrol</span>(1)</span></a> program (SIGUSR[1|2] signals are no longer
140 used since Samba 2.2). This is to allow transient problems to be diagnosed,
141 whilst still running at a normally low log level.</p><p>Note that as the signal handlers send a debug write,
142 they are not re-entrant in <span><strong class="command">smbd</strong></span>. This you should wait until
143 <span><strong class="command">smbd</strong></span> is in a state of waiting for an incoming SMB before
144 issuing them. It is possible to make the signal handlers safe
145 by un-blocking the signals before the select call and re-blocking
146 them after, however this would affect performance.</p></div><div class="refsect1" lang="en"><a name="id2498536"></a><h2>SEE ALSO</h2><p><a href="hosts_access.5.html"><span class="citerefentry"><span class="refentrytitle">hosts_access</span>(5)</span></a>, <a href="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the
147 Internet RFC's <code class="filename">rfc1001.txt</code>, <code class="filename">rfc1002.txt</code>.
148 In addition the CIFS (formerly SMB) specification is available
149 as a link from the Web page <a href="http://samba.org/cifs/" target="_top">
150 http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><a name="id2498622"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
151 were created by Andrew Tridgell. Samba is now developed
152 by the Samba Team as an Open Source project similar
153 to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer.
154 The man page sources were converted to YODL format (another
155 excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
156 ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
157 release by Jeremy Allison. The conversion to DocBook for
158 Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
159 Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
projects / samba / blob