diff options
| author | vorlon <vorlon@alioth.debian.org> | 2009-02-14 17:12:39 +0000 |
|---|---|---|
| committer | vorlon <vorlon@alioth.debian.org> | 2009-02-14 17:12:39 +0000 |
| commit | ca16c95b70df7e455b620a5d6eb9f224c725ae44 (patch) | |
| tree | 1b2bdb4d178b3e53eec9e5b6d59fa053b6bc86f6 /docs/htmldocs/Samba3-HOWTO/compiling.html | |
| parent | d113059e3e5c884802d6b8c2741e53247d8ff64e (diff) | |
| download | samba-ca16c95b70df7e455b620a5d6eb9f224c725ae44.tar.gz | |
Merge samba-3.3.0 into branches/samba/upstream.
git-svn-id: svn://svn.debian.org/svn/pkg-samba/branches/samba/upstream@2570 fc4039ab-9d04-0410-8cac-899223bdd6b0
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/compiling.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/compiling.html | 80 |
1 files changed, 40 insertions, 40 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/compiling.html b/docs/htmldocs/Samba3-HOWTO/compiling.html index 01b53251f9..b630eb3687 100644 --- a/docs/htmldocs/Samba3-HOWTO/compiling.html +++ b/docs/htmldocs/Samba3-HOWTO/compiling.html @@ -1,9 +1,9 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 42. How to Compile Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.1"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Appendix.html" title="Part VI. Reference Section"><link rel="next" href="Portability.html" title="Chapter 43. Portability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 42. How to Compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendix.html">Prev</a> </td><th width="60%" align="center">Part VI. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter 42. How to Compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div><div><p class="pubdate"> June 2005 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id2680542">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2680548">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2680589">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2680781">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2680855">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2680993">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2681231">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the <span class="application">smbd</span> <span class="application">nmbd</span> and <span class="application">winbindd</span></a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2681501">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2681721">Alternative: Starting <span class="application">smbd</span> as a Daemon</a></span></dt></dl></dd></dl></div><p> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 42. How to Compile Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Appendix.html" title="Part VI. Reference Section"><link rel="next" href="Portability.html" title="Chapter 43. Portability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 42. How to Compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendix.html">Prev</a> </td><th width="60%" align="center">Part VI. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter 42. How to Compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div><div><p class="pubdate"> June 2005 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id2687532">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687538">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687580">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687771">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687846">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687984">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688221">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688492">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688712">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></div><p> You can obtain the Samba source file from the <a class="ulink" href="http://samba.org/" target="_top">Samba Web site</a>. To obtain a development version, you can download Samba from Subversion or using <code class="literal">rsync</code>. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2680542"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2680548"></a>Introduction</h3></div></div></div><p> -<a class="indexterm" name="id2680556"></a> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687532"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687538"></a>Introduction</h3></div></div></div><p> +<a class="indexterm" name="id2687546"></a> Samba is developed in an open environment. Developers use a Subversion to “<span class="quote">checkin</span>” (also known as “<span class="quote">commit</span>”) new source code. Samba's various Subversion branches can @@ -12,13 +12,13 @@ detailed in this chapter. </p><p> This chapter is a modified version of the instructions found at the <a class="ulink" href="http://samba.org/samba/subversion.html" target="_top">Samba</a> Web site. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2680589"></a>Subversion Access to samba.org</h3></div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687580"></a>Subversion Access to samba.org</h3></div></div></div><p> The machine samba.org runs a publicly accessible Subversion repository for access to the source code of several packages, including Samba, rsync, distcc, ccache, and jitterbug. There are two main ways of accessing the Subversion server on this host. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2680603"></a>Access via ViewCVS</h4></div></div></div><p> -<a class="indexterm" name="id2680611"></a> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687593"></a>Access via ViewCVS</h4></div></div></div><p> +<a class="indexterm" name="id2687601"></a> You can access the source code via your favorite WWW browser. This allows you to access the contents of individual files in the repository and also to look at the revision history and commit logs of individual files. You can also ask for a diff @@ -26,8 +26,8 @@ listing between any two versions on the repository. </p><p> Use the URL <a class="ulink" href="http://viewcvs.samba.org/" target="_top">http://viewcvs.samba.org/</a>. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2680639"></a>Access via Subversion</h4></div></div></div><p> -<a class="indexterm" name="id2680647"></a> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687629"></a>Access via Subversion</h4></div></div></div><p> +<a class="indexterm" name="id2687637"></a> You can also access the source code via a normal Subversion client. This gives you much more control over what you can do with the repository and allows you to check out whole source trees and keep them up to date via normal Subversion commands. This is the preferred method of access if you are a developer and not just a @@ -37,7 +37,7 @@ a Subversion client. Your distribution might include one, or you can download th sources from <a class="ulink" href="http://subversion.tigris.org/" target="_top">http://subversion.tigris.org/</a>. </p><p> To gain access via anonymous Subversion, use the following steps. -</p><div class="procedure"><a name="id2680680"></a><p class="title"><b>Procedure 42.1. Retrieving Samba using Subversion</b></p><ol type="1"><li><p> +</p><div class="procedure"><a name="id2687670"></a><p class="title"><b>Procedure 42.1. Retrieving Samba using Subversion</b></p><ol type="1"><li><p> Install a recent copy of Subversion. All you really need is a copy of the Subversion client binary. </p></li><li><p> @@ -62,9 +62,9 @@ To gain access via anonymous Subversion, use the following steps. </p><pre class="screen"> <strong class="userinput"><code>svn update</code></strong> </pre><p> - </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2680781"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p> - <a class="indexterm" name="id2680789"></a> - <a class="indexterm" name="id2680796"></a> + </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687771"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p> + <a class="indexterm" name="id2687779"></a> + <a class="indexterm" name="id2687786"></a> <em class="parameter"><code>pserver.samba.org</code></em> also exports unpacked copies of most parts of the Subversion tree at the Samba <a class="ulink" href="ftp://pserver.samba.org/pub/unpacked" target="_top">pserver</a> location and also via anonymous rsync at the Samba <a class="ulink" href="rsync://pserver.samba.org/ftp/unpacked/" target="_top">rsync</a> server location. I recommend using rsync rather @@ -74,9 +74,9 @@ To gain access via anonymous Subversion, use the following steps. The disadvantage of the unpacked trees is that they do not support automatic merging of local changes as Subversion does. <code class="literal">rsync</code> access is most convenient for an initial install. - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2680855"></a>Verifying Samba's PGP Signature</h2></div></div></div><p> -<a class="indexterm" name="id2680864"></a> -<a class="indexterm" name="id2680870"></a> + </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687846"></a>Verifying Samba's PGP Signature</h2></div></div></div><p> +<a class="indexterm" name="id2687854"></a> +<a class="indexterm" name="id2687860"></a> 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. @@ -87,7 +87,7 @@ With that said, go ahead and download the following files: <code class="prompt">$ </code><strong class="userinput"><code>wget http://us1.samba.org/samba/ftp/samba-3.0.20.tar.asc</code></strong> <code class="prompt">$ </code><strong class="userinput"><code>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</code></strong> </pre><p> -<a class="indexterm" name="id2680918"></a> +<a class="indexterm" name="id2687908"></a> 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: </p><pre class="screen"> @@ -105,9 +105,9 @@ example of what you would not want to see would be: </p><pre class="screen"> gpg: BAD signature from “<span class="quote">Samba Distribution Verification Key</span>” </pre><p> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2680993"></a>Building the Binaries</h2></div></div></div><p> - <a class="indexterm" name="id2681001"></a> -<a class="indexterm" name="id2681008"></a> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687984"></a>Building the Binaries</h2></div></div></div><p> + <a class="indexterm" name="id2687992"></a> +<a class="indexterm" name="id2687998"></a> After the source tarball has been unpacked, the next step involves configuration to match Samba to your operating system platform. If your source directory does not contain the <code class="literal">configure</code> script, @@ -120,7 +120,7 @@ gpg: BAD signature from “<span class="quote">Samba Distribution Verificati <code class="prompt">root# </code> ./autogen.sh </pre><p> </p><p> - <a class="indexterm" name="id2681050"></a> + <a class="indexterm" name="id2688040"></a> To build the binaries, run the program <strong class="userinput"><code>./configure </code></strong> in the source directory. This should automatically configure Samba for your operating system. If you have unusual @@ -135,7 +135,7 @@ gpg: BAD signature from “<span class="quote">Samba Distribution Verificati <code class="prompt">root# </code><strong class="userinput"><code>./configure <em class="replaceable"><code>[... arguments ...]</code></em></code></strong> </pre><p> </p><p> - <a class="indexterm" name="id2681116"></a> + <a class="indexterm" name="id2688106"></a> Execute the following create the binaries: </p><pre class="screen"> <code class="prompt">root# </code> <strong class="userinput"><code>make</code></strong> @@ -164,7 +164,7 @@ gpg: BAD signature from “<span class="quote">Samba Distribution Verificati </pre><p> As you can see from this, building and installing Samba does not need to result in disaster! - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2681231"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p> + </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688221"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p> In order to compile Samba with ADS support, you need to have installed on your system: </p><div class="itemizedlist"><ul type="disc"><li><p> @@ -187,13 +187,13 @@ gpg: BAD signature from “<span class="quote">Samba Distribution Verificati If it does not, configure did not find your KRB5 libraries or your LDAP libraries. Look in <code class="filename">config.log</code> to figure out why and fix it. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681296"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688287"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p> </p><div class="itemizedlist"><ul type="disc"><li><p>libkrb5-dev</p></li><li><p>krb5-user</p></li></ul></div><p> - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681323"></a>Installing the Required Packages for Red Hat Linux</h4></div></div></div><p>On Red Hat Linux, this means you should have at least: </p><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688314"></a>Installing the Required Packages for Red Hat Linux</h4></div></div></div><p>On Red Hat Linux, this means you should have at least: </p><p> </p><div class="itemizedlist"><ul type="disc"><li><p>krb5-workstation (for kinit)</p></li><li><p>krb5-libs (for linking with)</p></li><li><p>krb5-devel (because you are compiling from source)</p></li></ul></div><p> </p><p>in addition to the standard development environment.</p><p>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.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681368"></a>SuSE Linux Package Requirements</h4></div></div></div><p> + about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688358"></a>SuSE Linux Package Requirements</h4></div></div></div><p> 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. @@ -204,7 +204,7 @@ gpg: BAD signature from “<span class="quote">Samba Distribution Verificati the maximum capabilities that are available. You should consider using SuSE-provided packages where they are available. </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="startingSamba"></a>Starting the <span class="application">smbd</span> <span class="application">nmbd</span> and <span class="application">winbindd</span></h2></div></div></div><p> - <a class="indexterm" name="id2681421"></a> + <a class="indexterm" name="id2688412"></a> You must choose to start <span class="application">smbd</span>, <span class="application">winbindd</span> and <span class="application">nmbd</span> either as daemons or from <span class="application">inetd</span>. Don't try to do both! Either you can put them in <code class="filename"> inetd.conf</code> and have them started on demand by @@ -216,7 +216,7 @@ gpg: BAD signature from “<span class="quote">Samba Distribution Verificati </p><p> The main advantage of starting <span class="application">smbd</span> and <span class="application">nmbd</span> using the recommended daemon method is that they will respond slightly more quickly to an initial connection request. - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2681501"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2681507"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if + </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688492"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2688498"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if you use NIS, NIS+, or LDAP to distribute services maps.</p></div><p>Look at your <code class="filename">/etc/services</code>. What is defined at port 139/tcp? If nothing is defined, then add a line like this:</p><pre class="programlisting">netbios-ssn 139/tcp</pre><p>Similarly for 137/udp, you should have an entry like:</p><pre class="programlisting">netbios-ns 137/udp</pre><p> @@ -225,12 +225,12 @@ gpg: BAD signature from “<span class="quote">Samba Distribution Verificati netbios-ssn stream tcp nowait root /usr/local/samba/sbin/smbd smbd netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd </pre><p> - </p><a class="indexterm" name="id2681569"></a><p> + </p><a class="indexterm" name="id2688560"></a><p> The exact syntax of <code class="filename">/etc/inetd.conf</code> varies between UNIXes. Look at the other entries in inetd.conf for a guide. </p><p> - <a class="indexterm" name="id2681590"></a> + <a class="indexterm" name="id2688580"></a> Some distributions use xinetd instead of inetd. Consult the xinetd manual for configuration information. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Some UNIXes already have entries like netbios_ns @@ -238,9 +238,9 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd You must edit <code class="filename">/etc/services</code> or <code class="filename">/etc/inetd.conf</code> to make them consistent. </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - <a class="indexterm" name="id2681627"></a> + <a class="indexterm" name="id2688618"></a> On many systems you may need to use the - <a class="link" href="smb.conf.5.html#INTERFACES">interfaces</a> option in <code class="filename">smb.conf</code> to specify + <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option in <code class="filename">smb.conf</code> to specify the IP address and netmask of your interfaces. Run <span class="application">ifconfig</span> as root if you do not know what the broadcast is for your net. <span class="application">nmbd</span> tries @@ -253,20 +253,20 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd </p></div><p> Restart <span class="application">inetd</span>, perhaps just send it a HUP, like this: -<a class="indexterm" name="id2681696"></a> +<a class="indexterm" name="id2688687"></a> </p><pre class="screen"> <code class="prompt">root# </code><strong class="userinput"><code>killall -HUP inetd</code></strong> </pre><p> - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2681721"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p> - <a class="indexterm" name="id2681735"></a> -<a class="indexterm" name="id2681742"></a> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688712"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p> + <a class="indexterm" name="id2688726"></a> +<a class="indexterm" name="id2688733"></a> To start the server as a daemon, you should create a script something like this one, perhaps calling it <code class="filename">startsmb</code>. </p><pre class="programlisting"> #!/bin/sh -/usr/local/samba/sbin/smbd -D -/usr/local/samba/sbin/winbindd -B -/usr/local/samba/sbin/nmbd -D +/usr/local/samba/sbin/smbd -D +/usr/local/samba/sbin/winbindd -D +/usr/local/samba/sbin/nmbd -D </pre><p> Make it executable with <code class="literal">chmod +x startsmb</code>. </p><p> @@ -278,7 +278,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd If you use the SVR4-style init system, you may like to look at the <code class="filename">examples/svr4-startup</code> script to make Samba fit into that system. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681820"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688811"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p> Red Hat Linux has not always included all Samba components in the standard installation. So versions of Red Hat Linux do not install the winbind utility, even though it is present on the installation CDROM media. Check to see if the <code class="literal">winbindd</code> is present @@ -311,7 +311,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd <code class="prompt">root# </code> chkconfig winbind on </pre><p> Samba will be started automatically at every system reboot. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2681942"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688933"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p> Novell SUSE Linux products automatically install all essential Samba components in a default installation. Configure your <code class="filename">smb.conf</code> file, then execute the following to start Samba: </p><pre class="screen"> |