21
21
can force a reload by sending a SIGHUP to the server. Reloading
22
22
the configuration file will not affect connections to any service
23
23
that is already established. Either the user will have to
24
disconnect from the service, or <code class="literal">smbd</code> killed and restarted.</p></div><div class="refsect1" lang="en"><a name="id2483608"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes
24
disconnect from the service, or <code class="literal">smbd</code> killed and restarted.</p></div><div class="refsect1" title="OPTIONS"><a name="id2489739"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes
25
25
the server to operate as a daemon. That is, it detaches
26
26
itself and runs in the background, fielding requests
27
27
on the appropriate port. Operating the server as a
60
60
investigating a problem. Levels above 3 are designed for
61
61
use only by developers and generate HUGE amounts of log
62
62
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
63
override the <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> parameter
64
in the <code class="filename">smb.conf</code> file.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the program version number.
65
</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the
63
override the <a class="link" href="smb.conf.5.html#" target="_top"></a> parameter
64
in the <code class="filename">smb.conf</code> file.</p></dd><dt><span class="term">-V|--version</span></dt><dd><p>Prints the program version number.
65
</p></dd><dt><span class="term">-s|--configfile <configuration file></span></dt><dd><p>The file specified contains the
66
66
configuration details required by the server. The
67
67
information in this file includes server-specific
68
68
information such as what printcap file to use, as well
82
82
number specifying the level of profiling data to be collected.
83
83
0 turns off profiling, 1 turns on counter profiling only,
84
84
2 turns on complete profiling, and 3 resets all profiling data.
85
</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481697"></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
85
</p></dd></dl></div></div><div class="refsect1" title="FILES"><a name="id2487661"></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
86
86
<code class="literal">inetd</code> meta-daemon, this file
87
87
must contain suitable startup information for the
96
96
</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 class="citerefentry" 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
97
97
install this file are <code class="filename">/usr/samba/lib/smb.conf</code>
98
98
and <code class="filename">/etc/samba/smb.conf</code>.</p><p>This file describes all the services the server
99
is to make available to clients. See <a class="citerefentry" 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="id2481823"></a><h2>LIMITATIONS</h2><p>On some systems <code class="literal">smbd</code> cannot change uid back
99
is to make available to clients. See <a class="citerefentry" 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" title="LIMITATIONS"><a name="id2487787"></a><h2>LIMITATIONS</h2><p>On some systems <code class="literal">smbd</code> cannot change uid back
100
100
to root after a setuid() call. Such systems are called
101
101
trapdoor uid systems. If you have such a system,
102
102
you will be unable to connect from a client (such as a PC) as
103
103
two different users at once. Attempts to connect the
104
104
second user will result in access denied or
105
similar.</p></div><div class="refsect1" lang="en"><a name="id2481845"></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
105
similar.</p></div><div class="refsect1" title="ENVIRONMENT VARIABLES"><a name="id2487809"></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
106
106
printable services, most systems will use the value of
107
107
this variable (or <code class="constant">lp</code> if this variable is
108
108
not defined) as the name of the printer to use. This
109
is not specific to the server, however.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481874"></a><h2>PAM INTERACTION</h2><p>Samba uses PAM for authentication (when presented with a plaintext
109
is not specific to the server, however.</p></dd></dl></div></div><div class="refsect1" title="PAM INTERACTION"><a name="id2487838"></a><h2>PAM INTERACTION</h2><p>Samba uses PAM for authentication (when presented with a plaintext
110
110
password), for account checking (is this account disabled?) and for
111
111
session management. The degree too which samba supports PAM is restricted
112
112
by the limitations of the SMB protocol and the <a class="link" href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions</a> <a class="citerefentry" 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:
113
</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Account Validation</em></span>: All accesses to a
113
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>Account Validation</em></span>: All accesses to a
114
114
samba server are checked
115
115
against PAM to see if the account is vaild, not disabled and is permitted to
116
116
login at this time. This also applies to encrypted logins.
117
</p></li><li><p><span class="emphasis"><em>Session Management</em></span>: When not using share
117
</p></li><li class="listitem"><p><span class="emphasis"><em>Session Management</em></span>: When not using share
118
118
level secuirty, users must pass PAM's session checks before access
119
119
is granted. Note however, that this is bypassed in share level secuirty.
120
120
Note also that some older pam configuration files may need a line
121
121
added for session support.
122
</p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481933"></a><h2>VERSION</h2><p>This man page is correct for version 3 of
123
the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481944"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the server are logged
122
</p></li></ul></div></div><div class="refsect1" title="VERSION"><a name="id2487897"></a><h2>VERSION</h2><p>This man page is correct for version 3 of
123
the Samba suite.</p></div><div class="refsect1" title="DIAGNOSTICS"><a name="id2487908"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the server are logged
124
124
in a specified log file. The log file name is specified
125
125
at compile time, but may be overridden on the command line.</p><p>The number and nature of diagnostics available depends
126
126
on the debug level used by the server. If you have problems, set
129
129
available in the source code to warrant describing each and every
130
130
diagnostic. At this stage your best bet is still to grep the
131
131
source code and inspect the conditions that gave rise to the
132
diagnostics you are seeing.</p></div><div class="refsect1" lang="en"><a name="id2481972"></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>
132
diagnostics you are seeing.</p></div><div class="refsect1" title="TDB FILES"><a name="id2487936"></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>
133
133
(*) information persistent across restarts (but not
134
134
necessarily important to backup).
135
</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="id2532666"></a><h2>SIGNALS</h2><p>Sending the <code class="literal">smbd</code> a SIGHUP will cause it to
135
</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" title="SIGNALS"><a name="id2538635"></a><h2>SIGNALS</h2><p>Sending the <code class="literal">smbd</code> a SIGHUP will cause it to
136
136
reload its <code class="filename">smb.conf</code> configuration
137
137
file within a short period of time.</p><p>To shut down a user's <code class="literal">smbd</code> process it is recommended
138
138
that <code class="literal">SIGKILL (-9)</code> <span class="emphasis"><em>NOT</em></span>
147
147
<code class="literal">smbd</code> is in a state of waiting for an incoming SMB before
148
148
issuing them. It is possible to make the signal handlers safe
149
149
by un-blocking the signals before the select call and re-blocking
150
them after, however this would affect performance.</p></div><div class="refsect1" lang="en"><a name="id2532752"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="hosts_access.5.html"><span class="citerefentry"><span class="refentrytitle">hosts_access</span>(5)</span></a>, <a class="citerefentry" href="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a class="citerefentry" href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the
150
them after, however this would affect performance.</p></div><div class="refsect1" title="SEE ALSO"><a name="id2538722"></a><h2>SEE ALSO</h2><p><a class="citerefentry" href="hosts_access.5.html"><span class="citerefentry"><span class="refentrytitle">hosts_access</span>(5)</span></a>, <a class="citerefentry" href="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a class="citerefentry" href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the
151
151
Internet RFC's <code class="filename">rfc1001.txt</code>, <code class="filename">rfc1002.txt</code>.
152
152
In addition the CIFS (formerly SMB) specification is available
153
153
as a link from the Web page <a class="ulink" href="http://samba.org/cifs/" target="_top">
154
http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><a name="id2532832"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
154
http://samba.org/cifs/</a>.</p></div><div class="refsect1" title="AUTHOR"><a name="id2538802"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
155
155
were created by Andrew Tridgell. Samba is now developed
156
156
by the Samba Team as an Open Source project similar
157
157
to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer.