Table of Contents
You can obtain the Samba source file from the
Samba Web site. To obtain a development version,
you can download Samba from Subversion or using rsync
.
Samba is developed in an open environment. Developers use GIT to “checkin” (also known as “commit”) new source code. See the Using Git for Samba Development page in the Samba wiki.
pserver.samba.org
also exports unpacked copies of most parts of the Subversion tree
at the Samba unpacked location and also
via anonymous rsync at the Samba rsync server location. I recommend using rsync rather
than ftp, because rsync is capable of compressing data streams, but it is also more useful than FTP because
during a partial update it will transfer only the data that is missing plus a small overhead. See the rsync home page for more info on rsync.
The disadvantage of the unpacked trees is that they do not support automatic
merging of local changes as GIT does. rsync
access is most convenient
for an initial install.
It is strongly recommended that you verify the PGP signature for any source file before installing it. Even if you're not downloading from a mirror site, verifying PGP signatures should be a standard reflex. Many people today use the GNU GPG tool set in place of PGP. GPG can substitute for PGP.
With that said, go ahead and download the following files:
$
wget https://www.samba.org/samba/ftp/samba-latest.tar.asc
$
wget https://www.samba.org/samba/ftp/samba-latest.tar.gz
$
wget https://www.samba.org/samba/ftp/samba-pubkey.asc
The first file is the PGP signature for the Samba source file; the other is the Samba public PGP key itself. Import the public PGP key with:
$
gpg --import samba-pubkey.asc
and verify the Samba source code integrity with:
$
gzip -d samba-latest.tar.gz
$
gpg --verify samba-latest.tar.asc
If you receive a message like, “Good signature from Samba Distribution Verification Key...,” then all is well. The warnings about trust relationships can be ignored. An example of what you would not want to see would be:
gpg: BAD signature from “Samba Distribution Verification Key”
To build the binaries, run the program ./configure
in the top level directory of the source tree. This should automatically
configure Samba for your operating system. If you have unusual
needs, then you may wish to first run:
root#
./configure --help
This will help you to see what special options can be enabled. Now execute
./configure
with any arguments it might need:
root#
./configure
[... arguments ...]
Execute the following create the binaries:
root#
make
Once it is successfully compiled, you can execute the command shown here to install the binaries and manual pages:
root#
make install
In order to compile Samba with ADS support, you need to have installed on your system:
The MIT or Heimdal Kerberos development libraries (either install from the sources or use a package).
The OpenLDAP development libraries.
If your Kerberos libraries are in a nonstandard location, then
remember to add the configure option
--with-krb5=
.
DIR
After you run configure, make sure that the
bin/default/include/config.h
it generates contain lines like this:
#define HAVE_KRB5 1 #define HAVE_LDAP 1
If it does not, configure did not find your KRB5 libraries or
your LDAP libraries. Look in bin/config.log
to figure
out why and fix it.
On Debian, you need to install the following packages:
libkrb5-dev
krb5-user
On Red Hat Linux, this means you should have at least:
krb5-workstation (for kinit)
krb5-libs (for linking with)
krb5-devel (because you are compiling from source)
in addition to the standard development environment.
If these files are not installed on your system, you should check the installation CDs to find which has them and install the files using your tool of choice. If in doubt about what tool to use, refer to the Red Hat Linux documentation.
SuSE Linux installs Heimdal packages that may be required to allow you to build binary packages. You should verify that the development libraries have been installed on your system.
SuSE Linux Samba RPMs support Kerberos. Please refer to the documentation for your SuSE Linux system for information regarding SuSE Linux specific configuration. Additionally, SuSE is very active in the maintenance of Samba packages that provide the maximum capabilities that are available. You should consider using SuSE-provided packages where they are available.
You must choose to start smbd, winbindd and nmbd either as daemons or from
inetd. Don't try to do both! Either you can put
them in inetd.conf
and have them started on demand by
inetd or xinetd, or you
can start them as daemons either from the command-line or in
/etc/rc.local
. See the man pages for details on the
command line options. Take particular care to read the bit about what user
you need to have to start Samba. In many cases, you must be root.
The main advantage of starting smbd and nmbd using the recommended daemon method is that they will respond slightly more quickly to an initial connection request.
To start the server as a daemon, you should create a script something
like this one, perhaps calling it startsmb
.
#!/bin/sh /usr/local/samba/sbin/smbd -D /usr/local/samba/sbin/winbindd -D /usr/local/samba/sbin/nmbd -D
Make it executable with chmod +x startsmb
.
You can then run startsmb
by hand or execute
it from /etc/rc.local
.
To kill it, send a kill signal to the processes nmbd and smbd.
If you use the SVR4-style init system, you may like to look at the
examples/svr4-startup
script to make Samba fit
into that system.
The process for starting Samba will now be outlined. Be sure to configure Samba's smb.conf
file before starting Samba. When configured, start Samba by executing:
root#
service smb startroot#
service winbind start
These steps will start nmbd, smbd and winbindd.
To ensure that these services will be automatically restarted when the system is rebooted execute:
root#
chkconfig smb onroot#
chkconfig winbind on
Samba will be started automatically at every system reboot.
Novell SUSE Linux products automatically install all essential Samba components in a default installation.
Configure your smb.conf
file, then execute the following to start Samba:
root#
rcnmb startroot#
rcsmb startroot#
rcwinbind start
Now execute these commands so that Samba will be started automatically following a system reboot:
root#
chkconfig nmb onroot#
chkconfig smb onroot#
chkconfig winbind on
The Samba services will now be started automatically following a system reboot.