Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services. An example of a service is the Apache Web server for which the daemon is called
httpd. In the case of Samba there are three daemons, two of which are needed as a minimum.
The Samba server is made up of the following daemons:
This daemon handles all name registration and resolution requests. It is the primary vehicle involved in network browsing. It handles all UDP-based protocols. The
nmbd daemon should be the first command started as part of the Samba startup process.
This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also manages local authentication. It should be started immediately following the startup of
This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when Samba has trust relationships with another domain. The
winbindd daemon will check the
smb.conf file for the presence of the
idmap uid and
idmap gid parameters. If they are are found,
winbindd will use the values specified for for UID and GID allocation. If these parameters are not specified,
winbindd will start but it will not be able to allocate UIDs or GIDs.
When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its integration into the platform as a whole. Please refer to your operating system platform administration manuals for specific information pertaining to correct management of Samba startup.