| 1 | '\" t | 
|---|
| 2 | .\"     Title: smbd | 
|---|
| 3 | .\"    Author: [see the "AUTHOR" section] | 
|---|
| 4 | .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> | 
|---|
| 5 | .\"      Date: 08/02/2011 | 
|---|
| 6 | .\"    Manual: System Administration tools | 
|---|
| 7 | .\"    Source: Samba 3.5 | 
|---|
| 8 | .\"  Language: English | 
|---|
| 9 | .\" | 
|---|
| 10 | .TH "SMBD" "8" "08/02/2011" "Samba 3\&.5" "System Administration tools" | 
|---|
| 11 | .\" ----------------------------------------------------------------- | 
|---|
| 12 | .\" * set default formatting | 
|---|
| 13 | .\" ----------------------------------------------------------------- | 
|---|
| 14 | .\" disable hyphenation | 
|---|
| 15 | .nh | 
|---|
| 16 | .\" disable justification (adjust text to left margin only) | 
|---|
| 17 | .ad l | 
|---|
| 18 | .\" ----------------------------------------------------------------- | 
|---|
| 19 | .\" * MAIN CONTENT STARTS HERE * | 
|---|
| 20 | .\" ----------------------------------------------------------------- | 
|---|
| 21 | .SH "NAME" | 
|---|
| 22 | smbd \- server to provide SMB/CIFS services to clients | 
|---|
| 23 | .SH "SYNOPSIS" | 
|---|
| 24 | .HP \w'\ 'u | 
|---|
| 25 | smbd [\-D] [\-F] [\-S] [\-i] [\-h] [\-V] [\-b] [\-d\ <debug\ level>] [\-l\ <log\ directory>] [\-p\ <port\ number(s)>] [\-P\ <profiling\ level>] [\-O\ <socket\ option>] [\-s\ <configuration\ file>] | 
|---|
| 26 | .SH "DESCRIPTION" | 
|---|
| 27 | .PP | 
|---|
| 28 | This program is part of the | 
|---|
| 29 | \fBsamba\fR(7) | 
|---|
| 30 | suite\&. | 
|---|
| 31 | .PP | 
|---|
| 32 | smbd | 
|---|
| 33 | is the server daemon that provides filesharing and printing services to Windows clients\&. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol\&. This is compatible with the LanManager protocol, and can service LanManager clients\&. These include MSCLIENT 3\&.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux\&. | 
|---|
| 34 | .PP | 
|---|
| 35 | An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those services (see | 
|---|
| 36 | \fBsmb.conf\fR(5)\&. This man page will not describe the services, but will concentrate on the administrative aspects of running the server\&. | 
|---|
| 37 | .PP | 
|---|
| 38 | Please note that there are significant security implications to running this server, and the | 
|---|
| 39 | \fBsmb.conf\fR(5) | 
|---|
| 40 | manual page should be regarded as mandatory reading before proceeding with installation\&. | 
|---|
| 41 | .PP | 
|---|
| 42 | A session is created whenever a client requests one\&. Each client gets a copy of the server for each session\&. This copy then services all connections made by the client during that session\&. When all connections from its client are closed, the copy of the server for that client terminates\&. | 
|---|
| 43 | .PP | 
|---|
| 44 | The configuration file, and any files that it includes, are automatically reloaded every minute, if they change\&. You can force a reload by sending a SIGHUP to the server\&. Reloading the configuration file will not affect connections to any service that is already established\&. Either the user will have to disconnect from the service, or | 
|---|
| 45 | smbd | 
|---|
| 46 | killed and restarted\&. | 
|---|
| 47 | .SH "OPTIONS" | 
|---|
| 48 | .PP | 
|---|
| 49 | \-D | 
|---|
| 50 | .RS 4 | 
|---|
| 51 | If specified, this parameter causes the server to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\&. Operating the server as a daemon is the recommended way of running | 
|---|
| 52 | smbd | 
|---|
| 53 | for servers that provide more than casual use file and print services\&. This switch is assumed if | 
|---|
| 54 | smbd | 
|---|
| 55 | is executed on the command line of a shell\&. | 
|---|
| 56 | .RE | 
|---|
| 57 | .PP | 
|---|
| 58 | \-F | 
|---|
| 59 | .RS 4 | 
|---|
| 60 | If specified, this parameter causes the main | 
|---|
| 61 | smbd | 
|---|
| 62 | process to not daemonize, i\&.e\&. double\-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running | 
|---|
| 63 | smbd | 
|---|
| 64 | under process supervisors such as | 
|---|
| 65 | supervise | 
|---|
| 66 | and | 
|---|
| 67 | svscan | 
|---|
| 68 | from Daniel J\&. Bernstein\'s | 
|---|
| 69 | daemontools | 
|---|
| 70 | package, or the AIX process monitor\&. | 
|---|
| 71 | .RE | 
|---|
| 72 | .PP | 
|---|
| 73 | \-S | 
|---|
| 74 | .RS 4 | 
|---|
| 75 | If specified, this parameter causes | 
|---|
| 76 | smbd | 
|---|
| 77 | to log to standard output rather than a file\&. | 
|---|
| 78 | .RE | 
|---|
| 79 | .PP | 
|---|
| 80 | \-i | 
|---|
| 81 | .RS 4 | 
|---|
| 82 | If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit daemon mode when run from the command line\&. | 
|---|
| 83 | smbd | 
|---|
| 84 | also logs to standard output, as if the | 
|---|
| 85 | \-S | 
|---|
| 86 | parameter had been given\&. | 
|---|
| 87 | .RE | 
|---|
| 88 | .PP | 
|---|
| 89 | \-d|\-\-debuglevel=level | 
|---|
| 90 | .RS 4 | 
|---|
| 91 | \fIlevel\fR | 
|---|
| 92 | is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&. | 
|---|
| 93 | .sp | 
|---|
| 94 | The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&. | 
|---|
| 95 | .sp | 
|---|
| 96 | Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. | 
|---|
| 97 | .sp | 
|---|
| 98 | Note that specifying this parameter here will override the | 
|---|
| 99 | \m[blue]\fB\%smb.conf.5.html#\fR\m[] | 
|---|
| 100 | parameter in the | 
|---|
| 101 | smb\&.conf | 
|---|
| 102 | file\&. | 
|---|
| 103 | .RE | 
|---|
| 104 | .PP | 
|---|
| 105 | \-V|\-\-version | 
|---|
| 106 | .RS 4 | 
|---|
| 107 | Prints the program version number\&. | 
|---|
| 108 | .RE | 
|---|
| 109 | .PP | 
|---|
| 110 | \-s|\-\-configfile <configuration file> | 
|---|
| 111 | .RS 4 | 
|---|
| 112 | The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See | 
|---|
| 113 | smb\&.conf | 
|---|
| 114 | for more information\&. The default configuration file name is determined at compile time\&. | 
|---|
| 115 | .RE | 
|---|
| 116 | .PP | 
|---|
| 117 | \-l|\-\-log\-basename=logdirectory | 
|---|
| 118 | .RS 4 | 
|---|
| 119 | Base directory name for log/debug files\&. The extension | 
|---|
| 120 | \fB"\&.progname"\fR | 
|---|
| 121 | will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&. | 
|---|
| 122 | .RE | 
|---|
| 123 | .PP | 
|---|
| 124 | \-h|\-\-help | 
|---|
| 125 | .RS 4 | 
|---|
| 126 | Print a summary of command line options\&. | 
|---|
| 127 | .RE | 
|---|
| 128 | .PP | 
|---|
| 129 | \-b | 
|---|
| 130 | .RS 4 | 
|---|
| 131 | Prints information about how Samba was built\&. | 
|---|
| 132 | .RE | 
|---|
| 133 | .PP | 
|---|
| 134 | \-p|\-\-port<port number(s)> | 
|---|
| 135 | .RS 4 | 
|---|
| 136 | \fIport number(s)\fR | 
|---|
| 137 | is a space or comma\-separated list of TCP ports smbd should listen on\&. The default value is taken from the | 
|---|
| 138 | \m[blue]\fBports\fR\m[] | 
|---|
| 139 | parameter in | 
|---|
| 140 | smb\&.conf | 
|---|
| 141 | .sp | 
|---|
| 142 | The default ports are 139 (used for SMB over NetBIOS over TCP) and port 445 (used for plain SMB over TCP)\&. | 
|---|
| 143 | .RE | 
|---|
| 144 | .PP | 
|---|
| 145 | \-P|\-\-profiling\-level<profiling level> | 
|---|
| 146 | .RS 4 | 
|---|
| 147 | \fIprofiling level\fR | 
|---|
| 148 | is a number specifying the level of profiling data to be collected\&. 0 turns off profiling, 1 turns on counter profiling only, 2 turns on complete profiling, and 3 resets all profiling data\&. | 
|---|
| 149 | .RE | 
|---|
| 150 | .SH "FILES" | 
|---|
| 151 | .PP | 
|---|
| 152 | /etc/inetd\&.conf | 
|---|
| 153 | .RS 4 | 
|---|
| 154 | If the server is to be run by the | 
|---|
| 155 | inetd | 
|---|
| 156 | meta\-daemon, this file must contain suitable startup information for the meta\-daemon\&. | 
|---|
| 157 | .RE | 
|---|
| 158 | .PP | 
|---|
| 159 | /etc/rc | 
|---|
| 160 | .RS 4 | 
|---|
| 161 | or whatever initialization script your system uses)\&. | 
|---|
| 162 | .sp | 
|---|
| 163 | If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&. | 
|---|
| 164 | .RE | 
|---|
| 165 | .PP | 
|---|
| 166 | /etc/services | 
|---|
| 167 | .RS 4 | 
|---|
| 168 | If running the server via the meta\-daemon | 
|---|
| 169 | inetd, this file must contain a mapping of service name (e\&.g\&., netbios\-ssn) to service port (e\&.g\&., 139) and protocol type (e\&.g\&., tcp)\&. | 
|---|
| 170 | .RE | 
|---|
| 171 | .PP | 
|---|
| 172 | /usr/local/samba/lib/smb\&.conf | 
|---|
| 173 | .RS 4 | 
|---|
| 174 | This is the default location of the | 
|---|
| 175 | \fBsmb.conf\fR(5) | 
|---|
| 176 | server configuration file\&. Other common places that systems install this file are | 
|---|
| 177 | /usr/samba/lib/smb\&.conf | 
|---|
| 178 | and | 
|---|
| 179 | /etc/samba/smb\&.conf\&. | 
|---|
| 180 | .sp | 
|---|
| 181 | This file describes all the services the server is to make available to clients\&. See | 
|---|
| 182 | \fBsmb.conf\fR(5) | 
|---|
| 183 | for more information\&. | 
|---|
| 184 | .RE | 
|---|
| 185 | .SH "LIMITATIONS" | 
|---|
| 186 | .PP | 
|---|
| 187 | On some systems | 
|---|
| 188 | smbd | 
|---|
| 189 | cannot change uid back to root after a setuid() call\&. Such systems are called trapdoor uid systems\&. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once\&. Attempts to connect the second user will result in access denied or similar\&. | 
|---|
| 190 | .SH "ENVIRONMENT VARIABLES" | 
|---|
| 191 | .PP | 
|---|
| 192 | \fBPRINTER\fR | 
|---|
| 193 | .RS 4 | 
|---|
| 194 | If no printer name is specified to printable services, most systems will use the value of this variable (or | 
|---|
| 195 | \fBlp\fR | 
|---|
| 196 | if this variable is not defined) as the name of the printer to use\&. This is not specific to the server, however\&. | 
|---|
| 197 | .RE | 
|---|
| 198 | .SH "PAM INTERACTION" | 
|---|
| 199 | .PP | 
|---|
| 200 | Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management\&. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the | 
|---|
| 201 | \m[blue]\fBobey pam restrictions\fR\m[] | 
|---|
| 202 | \fBsmb.conf\fR(5) | 
|---|
| 203 | paramater\&. When this is set, the following restrictions apply: | 
|---|
| 204 | .sp | 
|---|
| 205 | .RS 4 | 
|---|
| 206 | .ie n \{\ | 
|---|
| 207 | \h'-04'\(bu\h'+03'\c | 
|---|
| 208 | .\} | 
|---|
| 209 | .el \{\ | 
|---|
| 210 | .sp -1 | 
|---|
| 211 | .IP \(bu 2.3 | 
|---|
| 212 | .\} | 
|---|
| 213 | \fIAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time\&. This also applies to encrypted logins\&. | 
|---|
| 214 | .RE | 
|---|
| 215 | .sp | 
|---|
| 216 | .RS 4 | 
|---|
| 217 | .ie n \{\ | 
|---|
| 218 | \h'-04'\(bu\h'+03'\c | 
|---|
| 219 | .\} | 
|---|
| 220 | .el \{\ | 
|---|
| 221 | .sp -1 | 
|---|
| 222 | .IP \(bu 2.3 | 
|---|
| 223 | .\} | 
|---|
| 224 | \fISession Management\fR: When not using share level secuirty, users must pass PAM\'s session checks before access is granted\&. Note however, that this is bypassed in share level secuirty\&. Note also that some older pam configuration files may need a line added for session support\&. | 
|---|
| 225 | .SH "VERSION" | 
|---|
| 226 | .PP | 
|---|
| 227 | This man page is correct for version 3 of the Samba suite\&. | 
|---|
| 228 | .SH "DIAGNOSTICS" | 
|---|
| 229 | .PP | 
|---|
| 230 | Most diagnostics issued by the server are logged in a specified log file\&. The log file name is specified at compile time, but may be overridden on the command line\&. | 
|---|
| 231 | .PP | 
|---|
| 232 | The number and nature of diagnostics available depends on the debug level used by the server\&. If you have problems, set the debug level to 3 and peruse the log files\&. | 
|---|
| 233 | .PP | 
|---|
| 234 | Most messages are reasonably self\-explanatory\&. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic\&. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing\&. | 
|---|
| 235 | .SH "TDB FILES" | 
|---|
| 236 | .PP | 
|---|
| 237 | Samba stores it\'s data in several TDB (Trivial Database) files, usually located in | 
|---|
| 238 | /var/lib/samba\&. | 
|---|
| 239 | .PP | 
|---|
| 240 | (*) information persistent across restarts (but not necessarily important to backup)\&. | 
|---|
| 241 | .PP | 
|---|
| 242 | account_policy\&.tdb* | 
|---|
| 243 | .RS 4 | 
|---|
| 244 | NT account policy settings such as pw expiration, etc\&.\&.\&. | 
|---|
| 245 | .RE | 
|---|
| 246 | .PP | 
|---|
| 247 | brlock\&.tdb | 
|---|
| 248 | .RS 4 | 
|---|
| 249 | byte range locks | 
|---|
| 250 | .RE | 
|---|
| 251 | .PP | 
|---|
| 252 | browse\&.dat | 
|---|
| 253 | .RS 4 | 
|---|
| 254 | browse lists | 
|---|
| 255 | .RE | 
|---|
| 256 | .PP | 
|---|
| 257 | connections\&.tdb | 
|---|
| 258 | .RS 4 | 
|---|
| 259 | share connections (used to enforce max connections, etc\&.\&.\&.) | 
|---|
| 260 | .RE | 
|---|
| 261 | .PP | 
|---|
| 262 | gencache\&.tdb | 
|---|
| 263 | .RS 4 | 
|---|
| 264 | generic caching db | 
|---|
| 265 | .RE | 
|---|
| 266 | .PP | 
|---|
| 267 | group_mapping\&.tdb* | 
|---|
| 268 | .RS 4 | 
|---|
| 269 | group mapping information | 
|---|
| 270 | .RE | 
|---|
| 271 | .PP | 
|---|
| 272 | locking\&.tdb | 
|---|
| 273 | .RS 4 | 
|---|
| 274 | share modes & oplocks | 
|---|
| 275 | .RE | 
|---|
| 276 | .PP | 
|---|
| 277 | login_cache\&.tdb* | 
|---|
| 278 | .RS 4 | 
|---|
| 279 | bad pw attempts | 
|---|
| 280 | .RE | 
|---|
| 281 | .PP | 
|---|
| 282 | messages\&.tdb | 
|---|
| 283 | .RS 4 | 
|---|
| 284 | Samba messaging system | 
|---|
| 285 | .RE | 
|---|
| 286 | .PP | 
|---|
| 287 | netsamlogon_cache\&.tdb* | 
|---|
| 288 | .RS 4 | 
|---|
| 289 | cache of user net_info_3 struct from net_samlogon() request (as a domain member) | 
|---|
| 290 | .RE | 
|---|
| 291 | .PP | 
|---|
| 292 | ntdrivers\&.tdb* | 
|---|
| 293 | .RS 4 | 
|---|
| 294 | installed printer drivers | 
|---|
| 295 | .RE | 
|---|
| 296 | .PP | 
|---|
| 297 | ntforms\&.tdb* | 
|---|
| 298 | .RS 4 | 
|---|
| 299 | installed printer forms | 
|---|
| 300 | .RE | 
|---|
| 301 | .PP | 
|---|
| 302 | ntprinters\&.tdb* | 
|---|
| 303 | .RS 4 | 
|---|
| 304 | installed printer information | 
|---|
| 305 | .RE | 
|---|
| 306 | .PP | 
|---|
| 307 | printing/ | 
|---|
| 308 | .RS 4 | 
|---|
| 309 | directory containing tdb per print queue of cached lpq output | 
|---|
| 310 | .RE | 
|---|
| 311 | .PP | 
|---|
| 312 | registry\&.tdb | 
|---|
| 313 | .RS 4 | 
|---|
| 314 | Windows registry skeleton (connect via regedit\&.exe) | 
|---|
| 315 | .RE | 
|---|
| 316 | .PP | 
|---|
| 317 | sessionid\&.tdb | 
|---|
| 318 | .RS 4 | 
|---|
| 319 | session information (e\&.g\&. support for \'utmp = yes\') | 
|---|
| 320 | .RE | 
|---|
| 321 | .PP | 
|---|
| 322 | share_info\&.tdb* | 
|---|
| 323 | .RS 4 | 
|---|
| 324 | share acls | 
|---|
| 325 | .RE | 
|---|
| 326 | .PP | 
|---|
| 327 | winbindd_cache\&.tdb | 
|---|
| 328 | .RS 4 | 
|---|
| 329 | winbindd\'s cache of user lists, etc\&.\&.\&. | 
|---|
| 330 | .RE | 
|---|
| 331 | .PP | 
|---|
| 332 | winbindd_idmap\&.tdb* | 
|---|
| 333 | .RS 4 | 
|---|
| 334 | winbindd\'s local idmap db | 
|---|
| 335 | .RE | 
|---|
| 336 | .PP | 
|---|
| 337 | wins\&.dat* | 
|---|
| 338 | .RS 4 | 
|---|
| 339 | wins database when \'wins support = yes\' | 
|---|
| 340 | .RE | 
|---|
| 341 | .SH "SIGNALS" | 
|---|
| 342 | .PP | 
|---|
| 343 | Sending the | 
|---|
| 344 | smbd | 
|---|
| 345 | a SIGHUP will cause it to reload its | 
|---|
| 346 | smb\&.conf | 
|---|
| 347 | configuration file within a short period of time\&. | 
|---|
| 348 | .PP | 
|---|
| 349 | To shut down a user\'s | 
|---|
| 350 | smbd | 
|---|
| 351 | process it is recommended that | 
|---|
| 352 | SIGKILL (\-9) | 
|---|
| 353 | \fINOT\fR | 
|---|
| 354 | be used, except as a last resort, as this may leave the shared memory area in an inconsistent state\&. The safe way to terminate an | 
|---|
| 355 | smbd | 
|---|
| 356 | is to send it a SIGTERM (\-15) signal and wait for it to die on its own\&. | 
|---|
| 357 | .PP | 
|---|
| 358 | The debug log level of | 
|---|
| 359 | smbd | 
|---|
| 360 | may be raised or lowered using | 
|---|
| 361 | \fBsmbcontrol\fR(1) | 
|---|
| 362 | program (SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&. | 
|---|
| 363 | .PP | 
|---|
| 364 | Note that as the signal handlers send a debug write, they are not re\-entrant in | 
|---|
| 365 | smbd\&. This you should wait until | 
|---|
| 366 | smbd | 
|---|
| 367 | is in a state of waiting for an incoming SMB before issuing them\&. It is possible to make the signal handlers safe by un\-blocking the signals before the select call and re\-blocking them after, however this would affect performance\&. | 
|---|
| 368 | .SH "SEE ALSO" | 
|---|
| 369 | .PP | 
|---|
| 370 | \fBhosts_access\fR(5), | 
|---|
| 371 | \fBinetd\fR(8), | 
|---|
| 372 | \fBnmbd\fR(8), | 
|---|
| 373 | \fBsmb.conf\fR(5), | 
|---|
| 374 | \fBsmbclient\fR(1), | 
|---|
| 375 | \fBtestparm\fR(1), | 
|---|
| 376 | \fBtestprns\fR(1), and the Internet RFC\'s | 
|---|
| 377 | rfc1001\&.txt, | 
|---|
| 378 | rfc1002\&.txt\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page | 
|---|
| 379 | http://samba\&.org/cifs/\&. | 
|---|
| 380 | .SH "AUTHOR" | 
|---|
| 381 | .PP | 
|---|
| 382 | The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. | 
|---|
| 383 | .PP | 
|---|
| 384 | The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at | 
|---|
| 385 | ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. | 
|---|