1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
3 <chapter id="compiling">
9 <pubdate> 22 May 2001 </pubdate>
10 <pubdate> 18 March 2003 </pubdate>
11 <pubdate> June 2005 </pubdate>
14 <title>How to Compile Samba</title>
17 You can obtain the Samba source file from the
18 <ulink url="http://samba.org/">Samba Web site</ulink>. To obtain a development version,
19 you can download Samba from Subversion or using <command>rsync</command>.
23 <title>Access Samba Source Code via GIT</title>
27 <title>Introduction</title>
30 <indexterm><primary>Subversion</primary></indexterm>
31 Samba is developed in an open environment. Developers use
32 GIT to <quote>checkin</quote> (also known as
33 <quote>commit</quote>) new source code. See the
35 url="https://wiki.samba.org/index.php/Using_Git_for_Samba_Development">Using
36 Git for Samba Development page</ulink> in the Samba wiki.
45 <title>Accessing the Samba Sources via rsync and ftp</title>
49 <indexterm><primary>rsync</primary></indexterm>
50 <indexterm><primary>ftp</primary></indexterm>
51 <parameter>pserver.samba.org</parameter> also exports unpacked copies of most parts of the Subversion tree
52 at the Samba <ulink noescape="1" url="ftp://pserver.samba.org/pub/unpacked">pserver</ulink> location and also
53 via anonymous rsync at the Samba <ulink noescape="1"
54 url="rsync://pserver.samba.org/ftp/unpacked/">rsync</ulink> server location. I recommend using rsync rather
55 than ftp, because rsync is capable of compressing data streams, but it is also more useful than FTP because
56 during a partial update it will transfer only the data that is missing plus a small overhead. See <ulink
57 noescape="1" url="http://rsync.samba.org/">the rsync home page</ulink> for more info on rsync.
61 The disadvantage of the unpacked trees is that they do not support automatic
62 merging of local changes as GIT does. <command>rsync</command> access is most convenient
63 for an initial install.
68 <title>Verifying Samba's PGP Signature</title>
71 <indexterm><primary>GPG</primary></indexterm>
72 <indexterm><primary>PGP</primary></indexterm>
73 It is strongly recommended that you verify the PGP signature for any source file before
74 installing it. Even if you're not downloading from a mirror site, verifying PGP signatures
75 should be a standard reflex. Many people today use the GNU GPG tool set in place of PGP.
76 GPG can substitute for PGP.
81 With that said, go ahead and download the following files:
85 &prompt;<userinput>wget http://us1.samba.org/samba/ftp/samba-3.0.20.tar.asc</userinput>
86 &prompt;<userinput>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</userinput>
91 <indexterm><primary>PGP</primary></indexterm>
92 The first file is the PGP signature for the Samba source file; the other is the Samba public
93 PGP key itself. Import the public PGP key with:
95 &prompt;<userinput>gpg --import samba-pubkey.asc</userinput>
97 and verify the Samba source code integrity with:
99 &prompt;<userinput>gzip -d samba-3.0.20.tar.gz</userinput>
100 &prompt;<userinput>gpg --verify samba-3.0.20.tar.asc</userinput>
105 If you receive a message like, <quote>Good signature from Samba Distribution Verification Key...,</quote>
106 then all is well. The warnings about trust relationships can be ignored. An
107 example of what you would not want to see would be:
109 gpg: BAD signature from <quote>Samba Distribution Verification Key</quote>
116 <title>Building the Binaries</title>
119 <indexterm><primary>autogen.sh</primary></indexterm>
120 <indexterm><primary>configure</primary></indexterm>
121 After the source tarball has been unpacked, the next step involves
122 configuration to match Samba to your operating system platform.
123 If your source directory does not contain the <command>configure</command> script,
124 it is necessary to build it before you can continue. Building of
125 the configure script requires the correct version of the autoconf
126 tool kit. Where the necessary version of autoconf is present,
127 the configure script can be generated by executing the following
128 (please note that in Samba 3.4.x, the directory is called source3 instead
131 &rootprompt; cd samba-3.0.20/source
132 &rootprompt; ./autogen.sh
138 <indexterm><primary>configure</primary></indexterm>
139 To build the binaries, run the program <userinput>./configure
140 </userinput> in the source directory. This should automatically
141 configure Samba for your operating system. If you have unusual
142 needs, then you may wish to first run:
144 &rootprompt;<userinput>./configure --help</userinput>
149 This will help you to see what special options can be enabled. Now execute
150 <userinput>./configure</userinput> with any arguments it might need:
152 &rootprompt;<userinput>./configure <replaceable>[... arguments ...]</replaceable></userinput>
157 <indexterm><primary>make</primary></indexterm>
158 Execute the following create the binaries:
160 &rootprompt; <userinput>make</userinput>
162 Once it is successfully compiled, you can execute the command shown here to
163 install the binaries and manual pages:
165 &rootprompt; <userinput>make install</userinput>
170 Some people prefer to install binary files and man pages separately. If this is
171 your wish, the binary files can be installed by executing:
173 &rootprompt; <userinput>make installbin</userinput>
175 The man pages can be installed using this command:
177 &rootprompt; <userinput>make installman</userinput>
182 Note that if you are upgrading from a previous version of Samba the old
183 versions of the binaries will be renamed with an <quote>.old</quote> extension.
184 You can go back to the previous version by executing:
186 &rootprompt; <userinput>make revert</userinput>
188 As you can see from this, building and installing Samba does not need to
194 <title>Compiling Samba with Active Directory Support</title>
197 In order to compile Samba with ADS support, you need to have installed
204 The MIT or Heimdal Kerberos development libraries
205 (either install from the sources or use a package).
209 The OpenLDAP development libraries.
215 If your Kerberos libraries are in a nonstandard location, then
216 remember to add the configure option
217 <option>--with-krb5=<replaceable>DIR</replaceable></option>.
221 After you run configure, make sure that the
222 <filename>include/config.h</filename> it generates contain lines like this:
230 If it does not, configure did not find your KRB5 libraries or
231 your LDAP libraries. Look in <filename>config.log</filename> to figure
236 <title>Installing the Required Packages for Debian</title>
238 <para>On Debian, you need to install the following packages:</para>
241 <listitem><para>libkrb5-dev</para></listitem>
242 <listitem><para>krb5-user</para></listitem>
248 <title>Installing the Required Packages for Red Hat Linux</title>
250 <para>On Red Hat Linux, this means you should have at least: </para>
253 <listitem><para>krb5-workstation (for kinit)</para></listitem>
254 <listitem><para>krb5-libs (for linking with)</para></listitem>
255 <listitem><para>krb5-devel (because you are compiling from source)</para></listitem>
259 <para>in addition to the standard development environment.</para>
261 <para>If these files are not installed on your system, you should check the installation
262 CDs to find which has them and install the files using your tool of choice. If in doubt
263 about what tool to use, refer to the Red Hat Linux documentation.</para>
268 <title>SuSE Linux Package Requirements</title>
271 SuSE Linux installs Heimdal packages that may be required to allow you to build
272 binary packages. You should verify that the development libraries have been installed on
277 SuSE Linux Samba RPMs support Kerberos. Please refer to the documentation for
278 your SuSE Linux system for information regarding SuSE Linux specific configuration.
279 Additionally, SuSE is very active in the maintenance of Samba packages that provide
280 the maximum capabilities that are available. You should consider using SuSE-provided
281 packages where they are available.
290 <sect1 id="startingSamba">
291 <title>Starting the &smbd; &nmbd; and &winbindd;</title>
295 <indexterm><primary>inetd</primary></indexterm>
296 You must choose to start &smbd;, &winbindd; and &nmbd; either as daemons or from
297 <application>inetd</application>. Don't try to do both! Either you can put
298 them in <filename> inetd.conf</filename> and have them started on demand by
299 <application>inetd</application> or <application>xinetd</application>, or you
300 can start them as daemons either from the command-line or in
301 <filename>/etc/rc.local</filename>. See the man pages for details on the
302 command line options. Take particular care to read the bit about what user
303 you need to have to start Samba. In many cases, you must be root.
307 The main advantage of starting &smbd; and &nmbd; using the recommended daemon method
308 is that they will respond slightly more quickly to an initial connection request.
312 <title>Starting from inetd.conf</title>
314 <indexterm><primary>inetd</primary></indexterm>
317 <para>The following will be different if
318 you use NIS, NIS+, or LDAP to distribute services maps.</para>
321 <para>Look at your <filename>/etc/services</filename>.
322 What is defined at port 139/tcp? If nothing is defined,
323 then add a line like this:</para>
325 <para><programlisting>netbios-ssn 139/tcp</programlisting></para>
327 <para>Similarly for 137/udp, you should have an entry like:</para>
329 <para><programlisting>netbios-ns 137/udp</programlisting></para>
332 Next, edit your <filename>/etc/inetd.conf</filename> and add two lines like this:
334 netbios-ssn stream tcp nowait root /usr/local/samba/sbin/smbd smbd
335 netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
339 <indexterm><primary>/etc/inetd.conf</primary></indexterm>
341 The exact syntax of <filename>/etc/inetd.conf</filename>
342 varies between UNIXes. Look at the other entries in inetd.conf
347 <indexterm><primary>xinetd</primary></indexterm>
348 Some distributions use xinetd instead of inetd. Consult the
349 xinetd manual for configuration information.
352 <note><para>Some UNIXes already have entries like netbios_ns
353 (note the underscore) in <filename>/etc/services</filename>.
354 You must edit <filename>/etc/services</filename> or
355 <filename>/etc/inetd.conf</filename> to make them consistent.
359 <indexterm><primary>ifconfig</primary></indexterm>
360 On many systems you may need to use the
361 <smbconfoption name="interfaces"/> option in &smb.conf; to specify
362 the IP address and netmask of your interfaces. Run
363 <application>ifconfig</application> as root if you do
364 not know what the broadcast is for your net. &nmbd; tries
365 to determine it at runtime, but fails on some UNIXes.
369 Many UNIXes only accept around five parameters on the command
370 line in <filename>inetd.conf</filename>. This means you shouldn't
371 use spaces between the options and arguments, or you should use
372 a script and start the script from <command>inetd</command>.
376 Restart <application>inetd</application>, perhaps just send it a HUP,
378 <indexterm><primary>killall</primary></indexterm>
380 &rootprompt;<userinput>killall -HUP inetd</userinput>
387 <title>Alternative: Starting &smbd; as a Daemon</title>
390 <indexterm><primary>daemon</primary></indexterm>
391 <indexterm><primary>startsmb</primary></indexterm>
392 To start the server as a daemon, you should create a script something
393 like this one, perhaps calling it <filename>startsmb</filename>.
396 <para><programlisting>
398 /usr/local/samba/sbin/smbd -D
399 /usr/local/samba/sbin/winbindd -D
400 /usr/local/samba/sbin/nmbd -D
401 </programlisting></para>
404 Make it executable with <command>chmod +x startsmb</command>.
408 You can then run <command>startsmb</command> by hand or execute
409 it from <filename>/etc/rc.local</filename>.
413 To kill it, send a kill signal to the processes &nmbd; and &smbd;.
417 If you use the SVR4-style init system, you may like to look at the
418 <filename>examples/svr4-startup</filename> script to make Samba fit
423 <title>Starting Samba for Red Hat Linux</title>
426 Red Hat Linux has not always included all Samba components in the standard installation.
427 So versions of Red Hat Linux do not install the winbind utility, even though it is present
428 on the installation CDROM media. Check to see if the <command>winbindd</command> is present
431 &rootprompt; ls /usr/sbin/winbindd
434 This means that the appropriate RPM package was installed. The following response means
435 that it is not installed:
437 /bin/ls: /usr/sbin/winbind: No such file or directory
439 In this case, it should be installed if you intend to use <command>winbindd</command>. Search
440 the CDROM installation media for the samba-winbind RPM and install it following Red Hat
445 The process for starting Samba will now be outlined. Be sure to configure Samba's &smb.conf;
446 file before starting Samba. When configured, start Samba by executing:
448 &rootprompt; service smb start
449 &rootprompt; service winbind start
451 These steps will start &nmbd;, &smbd; and &winbindd;.
455 To ensure that these services will be automatically restarted when the system is rebooted
458 &rootprompt; chkconfig smb on
459 &rootprompt; chkconfig winbind on
461 Samba will be started automatically at every system reboot.
467 <title>Starting Samba for Novell SUSE Linux</title>
470 Novell SUSE Linux products automatically install all essential Samba components in a default installation.
471 Configure your &smb.conf; file, then execute the following to start Samba:
473 &rootprompt; rcnmb start
474 &rootprompt; rcsmb start
475 &rootprompt; rcwinbind start
477 Now execute these commands so that Samba will be started automatically following a system
480 &rootprompt; chkconfig nmb on
481 &rootprompt; chkconfig smb on
482 &rootprompt; chkconfig winbind on
484 The Samba services will now be started automatically following a system reboot.