source: trunk/samba/docs/manpages/smbd.8@ 104

Last change on this file since 104 was 44, checked in by Paul Smedley, 18 years ago

Update source to 3.0.25b

File size: 12.6 KB
RevLine 
[39]1.\"Generated by db2man.xsl. Don't modify this, modify the source.
2.de Sh \" Subsection
3.br
4.if t .Sp
5.ne 5
6.PP
7\fB\\$1\fR
8.PP
9..
10.de Sp \" Vertical space (when we can't use .PP)
11.if t .sp .5v
12.if n .sp
13..
14.de Ip \" List item
15.br
16.ie \\n(.$>=3 .ne \\$3
17.el .ne 3
18.IP "\\$1" \\$2
19..
20.TH "SMBD" 8 "" "" ""
21.SH "NAME"
22smbd - server to provide SMB/CIFS services to clients
23.SH "SYNOPSIS"
[44]24.HP 1
25smbd [-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>]
[39]26.SH "DESCRIPTION"
27.PP
28This program is part of the
29\fBsamba\fR(7)
30suite.
31.PP
[44]32smbd
[39]33is 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
35An 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
38Please note that there are significant security implications to running this server, and the
39\fBsmb.conf\fR(5)
40manual page should be regarded as mandatory reading before proceeding with installation.
41.PP
42A 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
44The 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
[44]45smbd
[39]46killed and restarted.
47.SH "OPTIONS"
48.PP
49-D
50.RS 3n
51If 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
[44]52smbd
[39]53for servers that provide more than casual use file and print services. This switch is assumed if
[44]54smbd
[39]55is executed on the command line of a shell.
56.RE
57.PP
58-F
59.RS 3n
60If specified, this parameter causes the main
[44]61smbd
[39]62process 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
[44]63smbd
[39]64under process supervisors such as
[44]65supervise
[39]66and
[44]67svscan
[39]68from Daniel J. Bernstein's
[44]69daemontools
[39]70package, or the AIX process monitor.
71.RE
72.PP
73-S
74.RS 3n
75If specified, this parameter causes
[44]76smbd
[39]77to log to standard output rather than a file.
78.RE
79.PP
80-i
81.RS 3n
82If 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 deamon mode when run from the command line.
[44]83smbd
[39]84also logs to standard output, as if the
[44]85-S
[39]86parameter had been given.
87.RE
88.PP
89-V
90.RS 3n
91Prints the program version number.
92.RE
93.PP
94-s <configuration file>
95.RS 3n
96The 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
97\fIsmb.conf\fR
98for more information. The default configuration file name is determined at compile time.
99.RE
100.PP
101-d|--debuglevel=level
102.RS 3n
103\fIlevel\fR
104is an integer from 0 to 10. The default value if this parameter is not specified is zero.
105.sp
106The 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.
107.sp
108Levels 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.
109.sp
110Note that specifying this parameter here will override the
111
112parameter in the
113\fIsmb.conf\fR
114file.
115.RE
116.PP
117-l|--logfile=logdirectory
118.RS 3n
119Base directory name for log/debug files. The extension
120\fB".progname"\fR
121will 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 3n
126Print a summary of command line options.
127.RE
128.PP
129-b
130.RS 3n
131Prints information about how Samba was built.
132.RE
133.PP
134-p|--port<port number(s)>
135.RS 3n
136\fIport number(s)\fR
137is a space or comma-separated list of TCP ports smbd should listen on. The default value is taken from the
138ports parameter in
139\fIsmb.conf\fR
140.sp
141The default ports are 139 (used for SMB over NetBIOS over TCP) and port 445 (used for plain SMB over TCP).
142.RE
143.PP
144-P|--profiling-level<profiling level>
145.RS 3n
146\fIprofiling level\fR
147is 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.
148.RE
149.SH "FILES"
150.PP
151\fI/etc/inetd.conf\fR
152.RS 3n
153If the server is to be run by the
[44]154inetd
[39]155meta-daemon, this file must contain suitable startup information for the meta-daemon.
156.RE
157.PP
158\fI/etc/rc\fR
159.RS 3n
160or whatever initialization script your system uses).
161.sp
162If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server.
163.RE
164.PP
165\fI/etc/services\fR
166.RS 3n
167If running the server via the meta-daemon
[44]168inetd, 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).
[39]169.RE
170.PP
171\fI/usr/local/samba/lib/smb.conf\fR
172.RS 3n
173This is the default location of the
174\fBsmb.conf\fR(5)
175server configuration file. Other common places that systems install this file are
176\fI/usr/samba/lib/smb.conf\fR
177and
178\fI/etc/samba/smb.conf\fR.
179.sp
180This file describes all the services the server is to make available to clients. See
181\fBsmb.conf\fR(5)
182for more information.
183.RE
184.SH "LIMITATIONS"
185.PP
186On some systems
[44]187smbd
[39]188cannot 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.
189.SH "ENVIRONMENT VARIABLES"
190.PP
191\fBPRINTER\fR
192.RS 3n
193If no printer name is specified to printable services, most systems will use the value of this variable (or
194\fBlp\fR
195if this variable is not defined) as the name of the printer to use. This is not specific to the server, however.
196.RE
197.SH "PAM INTERACTION"
198.PP
199Samba 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
200obey pam restrictions