Manual Pages for UNIX Darwin command on man smbd

SMBD(8) SMBD(8)

NAME

smbd - server to provide SMB/CIFS services to clients

SYNOPSIS

ssmmbbdd [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d ]

[-l ] [-p ] [-O ]

[-s ]

DESCRIPTION

This program is part of the ssaammbbaa(7) suite.

ssmmbbdd is the server daemon that provides filesharing and printing ser-

vices to Windows clients. The server provides filespace and printer

services to clients using the SMB (or CIFS) protocol. This is compati-

ble 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. An extensive description of the services that the server can provide is

given in the man page for the configuration file controlling the at-

tributes of those services (see ssmmbb..ccoonnff(5). This man page will not de-

scribe the services, but will concentrate on the administrative aspects of running the server. Please note that there are significant security implications to running this server, and the ssmmbb..ccoonnff(5) manual page should be regarded as mandatory reading before proceeding with installation. 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 con-

nections made by the client during that session. When all connections

from its client are closed, the copy of the server for that client ter-

minates.

The configuration file, and any files that it includes, are automati-

cally 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. Ei-

ther the user will have to disconnect from the service, or ssmmbbdd killed and restarted. OOPPTTIIOONNSS

-D 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 ssmmbbdd for servers that provide more than casual use file and print services. This switch is assumed if ssmmbbdd is executed on the command line of a shell.

-F If specified, this parameter causes the main ssmmbbdd process to not

daemonize, i.e. double-fork and disassociate with the terminal.

Child processes are still created as normal to service each con-

nection request, but the main process does not exit. This opera-

tion mode is suitable for runningssmmbbdd under process supervisors

such as ssuuppeerrvviissee and ssvvssccaann from Daniel J. Bernstein's ddaaeemmoonn-

ttoooollss package, or the AIX process monitor.

-S If specified, this parameter causesssmmbbdd to log to standard out-

put rather than a file.

-i If this parameter is specified it causes the server to run "in-

teractively", 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. ssmmbbdd also

logs to standard output, as if the -SS parameter had been given.

-V Prints the program version number.

-s

The file specified contains the configuration details required

by the server. The information in this file includes server-spe-

cific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

-d|-debug=debuglevel

debuglevel is an integer from 0 to 10. The default value if this parameter is not specified is zero. The higher this value, the more detail will be logged to the log

files about the activities of the server. At level 0, only crit-

ical 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. 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. Note that specifying this parameter here will override the log level parameter in the smb.conf file.

-l|-logfile=logdirectory

Base directory name for log/debug files. The extension ""..pprroogg-

nnaammee"" will be appended (e.g. log.smbclient, log.smbd, etc...).

The log file is never removed by the client.

-h|-help

Print a summary of command line options.

-b Prints information about how Samba was built.

-p

port number(s) is a space or comma-separated list of TCP ports

smbd should listen on. The default value is taken from the ports

parameter in smb.conf The default ports are 139 (used for SMB over NetBIOS over TCP) and port 445 (used for plain SMB over TCP). FILES /etc/inetd.conf

If the server is to be run by theiinneettdd meta-daemon, this file

must contain suitable startup information for the meta-daemon.

/etc/rc or whatever initialization script your system uses). If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. /etc/services

If running the server via the meta-daemon iinneettdd, 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). /usr/local/samba/lib/smb.conf

This is the default location of the ssmmbb..ccoonnff(5) server configu-

ration file. Other common places that systems install this file are /usr/samba/lib/smb.conf and /etc/samba/smb.conf. This file describes all the services the server is to make available to clients. See ssmmbb..ccoonnff(5) for more information. LLIIMMIITTAATTIIOONNSS On some systems ssmmbbdd 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. ENVIRONMENT VARIABLES PPRRIINNTTEERR

If no printer name is specified to printable services, most sys-

tems will use the value of this variable (or llpp if this variable is not defined) as the name of the printer to use. This is not specific to the server, however. PPAAMM IINNTTEERRAACCTTIIOONN 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 re-

stricted by the limitations of the SMB protocol and the obey pam re-

strictions ssmmbb..ccoonnff(5) paramater. When this is set, the following re-

strictions apply: +o AAccccoouunntt VVaalliiddaattiioonn: All accesses to a samba server are checked

against PAM to see if the account is vaild, not disabled and is per-

mitted to login at this time. This also applies to encrypted logins. +o SSeessssiioonn MMaannaaggeemmeenntt: 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 sup-

port. VVEERRSSIIOONN This man page is correct for version 3.0 of the Samba suite. DIAGNOSTICS 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 over-

ridden on the command line. 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.

Most messages are reasonably self-explanatory. Unfortunately, at the

time this man page was created, there are too many diagnostics avail-

able in the source code to warrant describing each and every diagnos-

tic. 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 see-

ing. TDB FILES Samba stores it's data in several TDB (Trivial Database) files, usually located in /var/lib/samba.

(*) information persistent across restarts (but not necessarily impor-

tant to backup). accountpolicy.tdb* NT account policy settings such as pw expiration, etc... brlock.tdb byte range locks browse.dat browse lists connections.tdb share connections (used to enforce max connections, etc...) gencache.tdb generic caching db groupmapping.tdb* group mapping information locking.tdb share modes & oplocks logincache.tdb* bad pw attempts messages.tdb Samba messaging system netsamlogoncache.tdb* cache of user netinfo3 struct from netsamlogon() request (as a domain member) ntdrivers.tdb* installed printer drivers ntforms.tdb* installed printer forms ntprinters.tdb* installed printer information printing/ directory containing tdb per print queue of cached lpq output registry.tdb Windows registry skeleton (connect via regedit.exe) sessionid.tdb session information (e.g. support for 'utmp = yes') shareinfo.tdb* share acls winbinddcache.tdb winbindd's cache of user lists, etc... winbinddidmap.tdb* winbindd's local idmap db wins.dat* wins database when 'wins support = yes' SSIIGGNNAALLSS

Sending the ssmmbbdd a SIGHUP will cause it to reload its smb.conf configu-

ration file within a short period of time.

To shut down a user's ssmmbbdd process it is recommended that SSIIGGKKIILLLL ((-99))

NNOOTT be used, except as a last resort, as this may leave the shared mem-

ory area in an inconsistent state. The safe way to terminate an ssmmbbdd is

to send it a SIGTERM (-15) signal and wait for it to die on its own.

The debug log level of ssmmbbdd may be raised or lowered using ssmmbbccoonn-

ttrrooll(1) 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. Note that as the signal handlers send a debug write, they are not

re-entrant in ssmmbbdd. This you should wait untilssmmbbdd 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.