- Timestamp:
- Mar 1, 2010, 3:05:48 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.3.x/docs/htmldocs/Samba3-HOWTO/compiling.html
r368 r411 1 <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.7 5.2"><link rel="home" href="index.html" title="The Official Samba 3.3.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" title="Chapter 42. How to Compile Samba"><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#id2693628">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2693634">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2693675">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2693866">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2693941">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2694079">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2694316">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#id2694587">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2694807">Alternative: Starting <span class="application">smbd</span>as a Daemon</a></span></dt></dl></dd></dl></div><p>1 <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.3.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#id2687543">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687549">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687590">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687781">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687856">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687994">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688231">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#id2688502">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688722">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></div><p> 2 2 You can obtain the Samba source file from the 3 3 <a class="ulink" href="http://samba.org/" target="_top">Samba Web site</a>. To obtain a development version, 4 4 you can download Samba from Subversion or using <code class="literal">rsync</code>. 5 </p><div class="sect1" title="Access Samba Source Code via Subversion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2693628"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" title="Introduction"><div class="titlepage"><div><div><h3 class="title"><a name="id2693634"></a>Introduction</h3></div></div></div><p>6 <a class="indexterm" name="id26 93642"></a>5 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687543"></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="id2687549"></a>Introduction</h3></div></div></div><p> 6 <a class="indexterm" name="id2687557"></a> 7 7 Samba is developed in an open environment. Developers use a 8 Subversion to <span class="quote">“<span class="quote">checkin</span>”</span>(also known as9 <span class="quote">“<span class="quote">commit</span>”</span>) new source code. Samba's various Subversion branches can8 Subversion to “<span class="quote">checkin</span>” (also known as 9 “<span class="quote">commit</span>”) new source code. Samba's various Subversion branches can 10 10 be accessed via anonymous Subversion using the instructions 11 11 detailed in this chapter. … … 13 13 This chapter is a modified version of the instructions found at the 14 14 <a class="ulink" href="http://samba.org/samba/subversion.html" target="_top">Samba</a> Web site. 15 </p></div><div class="sect2" title="Subversion Access to samba.org"><div class="titlepage"><div><div><h3 class="title"><a name="id2693675"></a>Subversion Access to samba.org</h3></div></div></div><p>15 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687590"></a>Subversion Access to samba.org</h3></div></div></div><p> 16 16 The machine samba.org runs a publicly accessible Subversion 17 17 repository for access to the source code of several packages, 18 18 including Samba, rsync, distcc, ccache, and jitterbug. There are two main ways 19 19 of accessing the Subversion server on this host. 20 </p><div class="sect3" title="Access via ViewCVS"><div class="titlepage"><div><div><h4 class="title"><a name="id2693689"></a>Access via ViewCVS</h4></div></div></div><p>21 <a class="indexterm" name="id26 93696"></a>20 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687603"></a>Access via ViewCVS</h4></div></div></div><p> 21 <a class="indexterm" name="id2687611"></a> 22 22 You can access the source code via your favorite WWW browser. This allows you to access 23 23 the contents of individual files in the repository and also to look at the revision … … 27 27 Use the URL 28 28 <a class="ulink" href="http://viewcvs.samba.org/" target="_top">http://viewcvs.samba.org/</a>. 29 </p></div><div class="sect3" title="Access via Subversion"><div class="titlepage"><div><div><h4 class="title"><a name="id2693724"></a>Access via Subversion</h4></div></div></div><p>30 <a class="indexterm" name="id26 93732"></a>29 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687639"></a>Access via Subversion</h4></div></div></div><p> 30 <a class="indexterm" name="id2687647"></a> 31 31 You can also access the source code via a normal Subversion client. This gives you much more control over what 32 32 you can do with the repository and allows you to check out whole source trees and keep them up to date via … … 38 38 </p><p> 39 39 To gain access via anonymous Subversion, use the following steps. 40 </p><div class="procedure" title="Procedure 42.1. Retrieving Samba using Subversion"><a name="id2693765"></a><p class="title"><b>Procedure 42.1. Retrieving Samba using Subversion</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p>40 </p><div class="procedure"><a name="id2687680"></a><p class="title"><b>Procedure 42.1. Retrieving Samba using Subversion</b></p><ol type="1"><li><p> 41 41 Install a recent copy of Subversion. All you really need is a 42 42 copy of the Subversion client binary. 43 </p></li><li class="step" title="Step 2"><p>43 </p></li><li><p> 44 44 Run the command 45 45 </p><pre class="screen"> … … 52 52 </p><p> 53 53 Subversion branches other then trunk can be obtained by adding branches/BRANCH_NAME to the URL you check 54 out. A list of branch names can be found on the <span class="quote">“<span class="quote">Development</span>”</span>page of the Samba Web site. A54 out. A list of branch names can be found on the “<span class="quote">Development</span>” page of the Samba Web site. A 55 55 common request is to obtain the latest 3.0 release code. This could be done by using the following command: 56 56 </p><pre class="screen"> 57 57 <strong class="userinput"><code>svn co svn://svnanon.samba.org/samba/branches/SAMBA_3_0 samba_3</code></strong>. 58 58 </pre><p> 59 </p></li><li class="step" title="Step 3"><p>59 </p></li><li><p> 60 60 Whenever you want to merge in the latest code changes, use the following command from within the Samba 61 61 directory: … … 63 63 <strong class="userinput"><code>svn update</code></strong> 64 64 </pre><p> 65 </p></li></ol></div></div></div></div><div class="sect1" title="Accessing the Samba Sources via rsync and ftp"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2693866"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p>66 <a class="indexterm" name="id26 93875"></a>67 <a class="indexterm" name="id26 93882"></a>65 </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="id2687781"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p> 66 <a class="indexterm" name="id2687790"></a> 67 <a class="indexterm" name="id2687796"></a> 68 68 <em class="parameter"><code>pserver.samba.org</code></em> also exports unpacked copies of most parts of the Subversion tree 69 69 at the Samba <a class="ulink" href="ftp://pserver.samba.org/pub/unpacked" target="_top">pserver</a> location and also … … 75 75 merging of local changes as Subversion does. <code class="literal">rsync</code> access is most convenient 76 76 for an initial install. 77 </p></div><div class="sect1" title="Verifying Samba's PGP Signature"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2693941"></a>Verifying Samba's PGP Signature</h2></div></div></div><p>78 <a class="indexterm" name="id26 93949"></a>79 <a class="indexterm" name="id26 93956"></a>77 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687856"></a>Verifying Samba's PGP Signature</h2></div></div></div><p> 78 <a class="indexterm" name="id2687864"></a> 79 <a class="indexterm" name="id2687870"></a> 80 80 It is strongly recommended that you verify the PGP signature for any source file before 81 81 installing it. Even if you're not downloading from a mirror site, verifying PGP signatures … … 88 88 <code class="prompt">$ </code><strong class="userinput"><code>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</code></strong> 89 89 </pre><p> 90 <a class="indexterm" name="id26 94004"></a>90 <a class="indexterm" name="id2687919"></a> 91 91 The first file is the PGP signature for the Samba source file; the other is the Samba public 92 92 PGP key itself. Import the public PGP key with: … … 100 100 </pre><p> 101 101 </p><p> 102 If you receive a message like, <span class="quote">“<span class="quote">Good signature from Samba Distribution Verification Key...,</span>”</span>102 If you receive a message like, “<span class="quote">Good signature from Samba Distribution Verification Key...,</span>” 103 103 then all is well. The warnings about trust relationships can be ignored. An 104 104 example of what you would not want to see would be: 105 105 </p><pre class="screen"> 106 gpg: BAD signature from <span class="quote">“<span class="quote">Samba Distribution Verification Key</span>”</span>107 </pre><p> 108 </p></div><div class="sect1" title="Building the Binaries"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2694079"></a>Building the Binaries</h2></div></div></div><p>109 <a class="indexterm" name="id26 94087"></a>110 <a class="indexterm" name="id26 94094"></a>106 gpg: BAD signature from “<span class="quote">Samba Distribution Verification Key</span>” 107 </pre><p> 108 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687994"></a>Building the Binaries</h2></div></div></div><p> 109 <a class="indexterm" name="id2688002"></a> 110 <a class="indexterm" name="id2688009"></a> 111 111 After the source tarball has been unpacked, the next step involves 112 112 configuration to match Samba to your operating system platform. … … 121 121 </pre><p> 122 122 </p><p> 123 <a class="indexterm" name="id26 94136"></a>123 <a class="indexterm" name="id2688051"></a> 124 124 To build the binaries, run the program <strong class="userinput"><code>./configure 125 125 </code></strong> in the source directory. This should automatically … … 136 136 </pre><p> 137 137 </p><p> 138 <a class="indexterm" name="id26 94201"></a>138 <a class="indexterm" name="id2688116"></a> 139 139 Execute the following create the binaries: 140 140 </p><pre class="screen"> … … 158 158 </p><p> 159 159 Note that if you are upgrading from a previous version of Samba the old 160 versions of the binaries will be renamed with an <span class="quote">“<span class="quote">.old</span>”</span>extension.160 versions of the binaries will be renamed with an “<span class="quote">.old</span>” extension. 161 161 You can go back to the previous version by executing: 162 162 </p><pre class="screen"> … … 165 165 As you can see from this, building and installing Samba does not need to 166 166 result in disaster! 167 </p><div class="sect2" title="Compiling Samba with Active Directory Support"><div class="titlepage"><div><div><h3 class="title"><a name="id2694316"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p>167 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688231"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p> 168 168 In order to compile Samba with ADS support, you need to have installed 169 169 on your system: 170 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>170 </p><div class="itemizedlist"><ul type="disc"><li><p> 171 171 The MIT or Heimdal Kerberos development libraries 172 172 (either install from the sources or use a package). 173 </p></li><li class="listitem"><p>173 </p></li><li><p> 174 174 The OpenLDAP development libraries. 175 175 </p></li></ul></div><p> … … 188 188 your LDAP libraries. Look in <code class="filename">config.log</code> to figure 189 189 out why and fix it. 190 </p><div class="sect3" title="Installing the Required Packages for Debian"><div class="titlepage"><div><div><h4 class="title"><a name="id2694382"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p>191 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>libkrb5-dev</p></li><li class="listitem"><p>krb5-user</p></li></ul></div><p>192 </p></div><div class="sect3" title="Installing the Required Packages for Red Hat Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id2694409"></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>193 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>krb5-workstation (for kinit)</p></li><li class="listitem"><p>krb5-libs (for linking with)</p></li><li class="listitem"><p>krb5-devel (because you are compiling from source)</p></li></ul></div><p>190 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688297"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p> 191 </p><div class="itemizedlist"><ul type="disc"><li><p>libkrb5-dev</p></li><li><p>krb5-user</p></li></ul></div><p> 192 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688324"></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> 193 </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> 194 194 </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 195 195 CDs to find which has them and install the files using your tool of choice. If in doubt 196 about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" title="SuSE Linux Package Requirements"><div class="titlepage"><div><div><h4 class="title"><a name="id2694454"></a>SuSE Linux Package Requirements</h4></div></div></div><p>196 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="id2688369"></a>SuSE Linux Package Requirements</h4></div></div></div><p> 197 197 SuSE Linux installs Heimdal packages that may be required to allow you to build 198 198 binary packages. You should verify that the development libraries have been installed on … … 204 204 the maximum capabilities that are available. You should consider using SuSE-provided 205 205 packages where they are available. 206 </p></div></div></div><div class="sect1" title="Starting the smbd nmbd and winbindd"><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>207 <a class="indexterm" name="id26 94508"></a>206 </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> 207 <a class="indexterm" name="id2688422"></a> 208 208 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 209 209 <span class="application">inetd</span>. Don't try to do both! Either you can put … … 217 217 The main advantage of starting <span class="application">smbd</span> and <span class="application">nmbd</span> using the recommended daemon method 218 218 is that they will respond slightly more quickly to an initial connection request. 219 </p><div class="sect2" title="Starting from inetd.conf"><div class="titlepage"><div><div><h3 class="title"><a name="id2694587"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2694593"></a><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if219 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688502"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2688508"></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 220 220 you use NIS, NIS+, or LDAP to distribute services maps.</p></div><p>Look at your <code class="filename">/etc/services</code>. 221 221 What is defined at port 139/tcp? If nothing is defined, … … 226 226 netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd 227 227 </pre><p> 228 </p><a class="indexterm" name="id26 94656"></a><p>228 </p><a class="indexterm" name="id2688571"></a><p> 229 229 The exact syntax of <code class="filename">/etc/inetd.conf</code> 230 230 varies between UNIXes. Look at the other entries in inetd.conf 231 231 for a guide. 232 232 </p><p> 233 <a class="indexterm" name="id26 94676"></a>233 <a class="indexterm" name="id2688591"></a> 234 234 Some distributions use xinetd instead of inetd. Consult the 235 235 xinetd manual for configuration information. 236 </p><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Some UNIXes already have entries like netbios_ns236 </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 237 237 (note the underscore) in <code class="filename">/etc/services</code>. 238 238 You must edit <code class="filename">/etc/services</code> or 239 239 <code class="filename">/etc/inetd.conf</code> to make them consistent. 240 </p></div><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>241 <a class="indexterm" name="id26 94714"></a>240 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 241 <a class="indexterm" name="id2688628"></a> 242 242 On many systems you may need to use the 243 243 <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option in <code class="filename">smb.conf</code> to specify … … 246 246 not know what the broadcast is for your net. <span class="application">nmbd</span> tries 247 247 to determine it at runtime, but fails on some UNIXes. 248 </p></div><div class="warning" title="Warning"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>248 </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> 249 249 Many UNIXes only accept around five parameters on the command 250 250 line in <code class="filename">inetd.conf</code>. This means you shouldn't … … 254 254 Restart <span class="application">inetd</span>, perhaps just send it a HUP, 255 255 like this: 256 <a class="indexterm" name="id26 94782"></a>256 <a class="indexterm" name="id2688697"></a> 257 257 </p><pre class="screen"> 258 258 <code class="prompt">root# </code><strong class="userinput"><code>killall -HUP inetd</code></strong> 259 259 </pre><p> 260 </p></div><div class="sect2" title="Alternative: Starting smbd as a Daemon"><div class="titlepage"><div><div><h3 class="title"><a name="id2694807"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p>261 <a class="indexterm" name="id26 94821"></a>262 <a class="indexterm" name="id26 94828"></a>260 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688722"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p> 261 <a class="indexterm" name="id2688736"></a> 262 <a class="indexterm" name="id2688743"></a> 263 263 To start the server as a daemon, you should create a script something 264 264 like this one, perhaps calling it <code class="filename">startsmb</code>. … … 275 275 </p><p> 276 276 To kill it, send a kill signal to the processes <span class="application">nmbd</span> and <span class="application">smbd</span>. 277 </p><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>277 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 278 278 If you use the SVR4-style init system, you may like to look at the 279 279 <code class="filename">examples/svr4-startup</code> script to make Samba fit 280 280 into that system. 281 </p></div><div class="sect3" title="Starting Samba for Red Hat Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id2694906"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p>281 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688821"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p> 282 282 Red Hat Linux has not always included all Samba components in the standard installation. 283 283 So versions of Red Hat Linux do not install the winbind utility, even though it is present … … 312 312 </pre><p> 313 313 Samba will be started automatically at every system reboot. 314 </p></div><div class="sect3" title="Starting Samba for Novell SUSE Linux"><div class="titlepage"><div><div><h4 class="title"><a name="id2695029"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p>314 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688944"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p> 315 315 Novell SUSE Linux products automatically install all essential Samba components in a default installation. 316 316 Configure your <code class="filename">smb.conf</code> file, then execute the following to start Samba:
Note:
See TracChangeset
for help on using the changeset viewer.
