1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
6 <refentrytitle>smbd</refentrytitle>
7 <manvolnum>8</manvolnum>
12 <refname>smbd</refname>
13 <refpurpose>server to provide SMB/CIFS services to clients</refpurpose>
18 <command>smbd</command>
19 <arg choice="opt">-D</arg>
20 <arg choice="opt">-F</arg>
21 <arg choice="opt">-S</arg>
22 <arg choice="opt">-i</arg>
23 <arg choice="opt">-h</arg>
24 <arg choice="opt">-V</arg>
25 <arg choice="opt">-b</arg>
26 <arg choice="opt">-d <debug level></arg>
27 <arg choice="opt">-l <log directory></arg>
28 <arg choice="opt">-p <port number(s)></arg>
29 <arg choice="opt">-P <profiling level></arg>
30 <arg choice="opt">-O <socket option></arg>
31 <arg choice="opt">-s <configuration file></arg>
36 <title>DESCRIPTION</title>
37 <para>This program is part of the <citerefentry><refentrytitle>samba</refentrytitle>
38 <manvolnum>7</manvolnum></citerefentry> suite.</para>
40 <para><command>smbd</command> is the server daemon that
41 provides filesharing and printing services to Windows clients.
42 The server provides filespace and printer services to
43 clients using the SMB (or CIFS) protocol. This is compatible
44 with the LanManager protocol, and can service LanManager
45 clients. These include MSCLIENT 3.0 for DOS, Windows for
46 Workgroups, Windows 95/98/ME, Windows NT, Windows 2000,
47 OS/2, DAVE for Macintosh, and smbfs for Linux.</para>
49 <para>An extensive description of the services that the
50 server can provide is given in the man page for the
51 configuration file controlling the attributes of those
52 services (see <citerefentry><refentrytitle>smb.conf</refentrytitle>
53 <manvolnum>5</manvolnum></citerefentry>. This man page will not describe the
54 services, but will concentrate on the administrative aspects
55 of running the server.</para>
57 <para>Please note that there are significant security
58 implications to running this server, and the <citerefentry><refentrytitle>smb.conf</refentrytitle>
59 <manvolnum>5</manvolnum></citerefentry> manual page should be regarded as mandatory reading before
60 proceeding with installation.</para>
62 <para>A session is created whenever a client requests one.
63 Each client gets a copy of the server for each session. This
64 copy then services all connections made by the client during
65 that session. When all connections from its client are closed,
66 the copy of the server for that client terminates.</para>
68 <para>The configuration file, and any files that it includes,
69 are automatically reloaded every minute, if they change. You
70 can force a reload by sending a SIGHUP to the server. Reloading
71 the configuration file will not affect connections to any service
72 that is already established. Either the user will have to
73 disconnect from the service, or <command>smbd</command> killed and restarted.</para>
77 <title>OPTIONS</title>
82 <listitem><para>If specified, this parameter causes
83 the server to operate as a daemon. That is, it detaches
84 itself and runs in the background, fielding requests
85 on the appropriate port. Operating the server as a
86 daemon is the recommended way of running <command>smbd</command> for
87 servers that provide more than casual use file and
88 print services. This switch is assumed if <command>smbd
89 </command> is executed on the command line of a shell.
95 <listitem><para>If specified, this parameter causes
96 the main <command>smbd</command> process to not daemonize,
97 i.e. double-fork and disassociate with the terminal.
98 Child processes are still created as normal to service
99 each connection request, but the main process does not
100 exit. This operation mode is suitable for running
101 <command>smbd</command> under process supervisors such
102 as <command>supervise</command> and <command>svscan</command>
103 from Daniel J. Bernstein's <command>daemontools</command>
104 package, or the AIX process monitor.
110 <listitem><para>If specified, this parameter causes
111 <command>smbd</command> to log to standard output rather
112 than a file.</para></listitem>
117 <listitem><para>If this parameter is specified it causes the
118 server to run "interactively", not as a daemon, even if the
119 server is executed on the command line of a shell. Setting this
120 parameter negates the implicit deamon mode when run from the
121 command line. <command>smbd</command> also logs to standard
122 output, as if the <command>-S</command> parameter had been
127 &stdarg.server.debug;
133 <listitem><para>Prints information about how
134 Samba was built.</para></listitem>
138 <term>-p|--port<port number(s)></term>
139 <listitem><para><replaceable>port number(s)</replaceable> is a
140 space or comma-separated list of TCP ports smbd should listen on.
141 The default value is taken from the <smbconfoption name="ports"/> parameter in &smb.conf;</para>
143 <para>The default ports are 139 (used for SMB over NetBIOS over TCP)
144 and port 445 (used for plain SMB over TCP).
149 <term>-P|--profiling-level<profiling level></term>
150 <listitem><para><replaceable>profiling level</replaceable> is a
151 number specifying the level of profiling data to be collected.
152 0 turns off profiling, 1 turns on counter profiling only,
153 2 turns on complete profiling, and 3 resets all profiling data.
164 <term><filename>/etc/inetd.conf</filename></term>
165 <listitem><para>If the server is to be run by the
166 <command>inetd</command> meta-daemon, this file
167 must contain suitable startup information for the
173 <term><filename>/etc/rc</filename></term>
174 <listitem><para>or whatever initialization script your
177 <para>If running the server as a daemon at startup,
178 this file will need to contain an appropriate startup
179 sequence for the server. </para></listitem>
183 <term><filename>/etc/services</filename></term>
184 <listitem><para>If running the server via the
185 meta-daemon <command>inetd</command>, this file
186 must contain a mapping of service name (e.g., netbios-ssn)
187 to service port (e.g., 139) and protocol type (e.g., tcp).
192 <term><filename>/usr/local/samba/lib/smb.conf</filename></term>
193 <listitem><para>This is the default location of the <citerefentry><refentrytitle>smb.conf</refentrytitle>
194 <manvolnum>5</manvolnum></citerefentry> server configuration file. Other common places that systems
195 install this file are <filename>/usr/samba/lib/smb.conf</filename>
196 and <filename>/etc/samba/smb.conf</filename>.</para>
198 <para>This file describes all the services the server
199 is to make available to clients. See <citerefentry><refentrytitle>smb.conf</refentrytitle>
200 <manvolnum>5</manvolnum></citerefentry> for more information.</para>
207 <title>LIMITATIONS</title>
208 <para>On some systems <command>smbd</command> cannot change uid back
209 to root after a setuid() call. Such systems are called
210 trapdoor uid systems. If you have such a system,
211 you will be unable to connect from a client (such as a PC) as
212 two different users at once. Attempts to connect the
213 second user will result in access denied or
218 <title>ENVIRONMENT VARIABLES</title>
222 <term><envar>PRINTER</envar></term>
223 <listitem><para>If no printer name is specified to
224 printable services, most systems will use the value of
225 this variable (or <constant>lp</constant> if this variable is
226 not defined) as the name of the printer to use. This
227 is not specific to the server, however.</para></listitem>
234 <title>PAM INTERACTION</title>
235 <para>Samba uses PAM for authentication (when presented with a plaintext
236 password), for account checking (is this account disabled?) and for
237 session management. The degree too which samba supports PAM is restricted
238 by the limitations of the SMB protocol and the <smbconfoption name="obey pam restrictions"/> <citerefentry><refentrytitle>smb.conf</refentrytitle>
239 <manvolnum>5</manvolnum></citerefentry> paramater. When this is set, the following restrictions apply:
243 <listitem><para><emphasis>Account Validation</emphasis>: All accesses to a
244 samba server are checked
245 against PAM to see if the account is vaild, not disabled and is permitted to
246 login at this time. This also applies to encrypted logins.
249 <listitem><para><emphasis>Session Management</emphasis>: When not using share
250 level secuirty, users must pass PAM's session checks before access
251 is granted. Note however, that this is bypassed in share level secuirty.
252 Note also that some older pam configuration files may need a line
253 added for session support.
259 <title>VERSION</title>
261 <para>This man page is correct for version 3.0 of
262 the Samba suite.</para>
266 <title>DIAGNOSTICS</title>
268 <para>Most diagnostics issued by the server are logged
269 in a specified log file. The log file name is specified
270 at compile time, but may be overridden on the command line.</para>
272 <para>The number and nature of diagnostics available depends
273 on the debug level used by the server. If you have problems, set
274 the debug level to 3 and peruse the log files.</para>
276 <para>Most messages are reasonably self-explanatory. Unfortunately,
277 at the time this man page was created, there are too many diagnostics
278 available in the source code to warrant describing each and every
279 diagnostic. At this stage your best bet is still to grep the
280 source code and inspect the conditions that gave rise to the
281 diagnostics you are seeing.</para>
285 <title>TDB FILES</title>
287 <para>Samba stores it's data in several TDB (Trivial Database) files, usually located in <filename>/var/lib/samba</filename>.</para>
290 (*) information persistent across restarts (but not
291 necessarily important to backup).
295 <varlistentry><term>account_policy.tdb*</term>
297 <para>NT account policy settings such as pw expiration, etc...</para>
301 <varlistentry><term>brlock.tdb</term>
302 <listitem><para>byte range locks</para></listitem>
305 <varlistentry><term>browse.dat</term>
306 <listitem><para>browse lists</para></listitem>
309 <varlistentry><term>connections.tdb</term>
310 <listitem><para>share connections (used to enforce max connections, etc...)</para></listitem>
313 <varlistentry><term>gencache.tdb</term>
314 <listitem><para>generic caching db</para></listitem>
317 <varlistentry><term>group_mapping.tdb*</term>
318 <listitem><para>group mapping information</para></listitem>
321 <varlistentry><term>locking.tdb</term>
322 <listitem><para>share modes & oplocks</para></listitem>
325 <varlistentry><term>login_cache.tdb*</term>
326 <listitem><para>bad pw attempts</para></listitem>
329 <varlistentry><term>messages.tdb</term>
330 <listitem><para>Samba messaging system</para></listitem>
333 <varlistentry><term>netsamlogon_cache.tdb*</term>
334 <listitem><para>cache of user net_info_3 struct from net_samlogon() request (as a domain member)</para></listitem>
337 <varlistentry><term>ntdrivers.tdb*</term>
338 <listitem><para>installed printer drivers</para></listitem>
341 <varlistentry><term>ntforms.tdb*</term>
342 <listitem><para>installed printer forms</para></listitem>
345 <varlistentry><term>ntprinters.tdb*</term>
346 <listitem><para>installed printer information</para></listitem>
349 <varlistentry><term>printing/</term>
350 <listitem><para>directory containing tdb per print queue of cached lpq output</para></listitem>
353 <varlistentry><term>registry.tdb</term>
354 <listitem><para>Windows registry skeleton (connect via regedit.exe)</para></listitem>
357 <varlistentry><term>sessionid.tdb</term>
358 <listitem><para>session information (e.g. support for 'utmp = yes')</para></listitem>
361 <varlistentry><term>share_info.tdb*</term>
362 <listitem><para>share acls</para></listitem>
365 <varlistentry><term>winbindd_cache.tdb</term>
366 <listitem><para>winbindd's cache of user lists, etc...</para></listitem>
369 <varlistentry><term>winbindd_idmap.tdb*</term>
370 <listitem><para>winbindd's local idmap db</para></listitem>
373 <varlistentry><term>wins.dat*</term>
374 <listitem><para>wins database when 'wins support = yes'</para></listitem>
382 <title>SIGNALS</title>
384 <para>Sending the <command>smbd</command> a SIGHUP will cause it to
385 reload its <filename>smb.conf</filename> configuration
386 file within a short period of time.</para>
388 <para>To shut down a user's <command>smbd</command> process it is recommended
389 that <command>SIGKILL (-9)</command> <emphasis>NOT</emphasis>
390 be used, except as a last resort, as this may leave the shared
391 memory area in an inconsistent state. The safe way to terminate
392 an <command>smbd</command> is to send it a SIGTERM (-15) signal and wait for
393 it to die on its own.</para>
395 <para>The debug log level of <command>smbd</command> may be raised
396 or lowered using <citerefentry><refentrytitle>smbcontrol</refentrytitle>
397 <manvolnum>1</manvolnum></citerefentry> program (SIGUSR[1|2] signals are no longer
398 used since Samba 2.2). This is to allow transient problems to be diagnosed,
399 whilst still running at a normally low log level.</para>
401 <para>Note that as the signal handlers send a debug write,
402 they are not re-entrant in <command>smbd</command>. This you should wait until
403 <command>smbd</command> is in a state of waiting for an incoming SMB before
404 issuing them. It is possible to make the signal handlers safe
405 by un-blocking the signals before the select call and re-blocking
406 them after, however this would affect performance.</para>
410 <title>SEE ALSO</title>
411 <para><citerefentry><refentrytitle>hosts_access</refentrytitle>
412 <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>inetd</refentrytitle>
413 <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>nmbd</refentrytitle>
414 <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle>
415 <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle>
416 <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle>
417 <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle>
418 <manvolnum>1</manvolnum></citerefentry>, and the
419 Internet RFC's <filename>rfc1001.txt</filename>, <filename>rfc1002.txt</filename>.
420 In addition the CIFS (formerly SMB) specification is available
421 as a link from the Web page <ulink noescape="1" url="http://samba.org/cifs/">
422 http://samba.org/cifs/</ulink>.</para>
426 <title>AUTHOR</title>
428 <para>The original Samba software and related utilities
429 were created by Andrew Tridgell. Samba is now developed
430 by the Samba Team as an Open Source project similar
431 to the way the Linux kernel is developed.</para>
433 <para>The original Samba man pages were written by Karl Auer.
434 The man page sources were converted to YODL format (another
435 excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
436 ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0
437 release by Jeremy Allison. The conversion to DocBook for
438 Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
439 Samba 3.0 was done by Alexander Bokovoy.</para>