1
0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00

docs: Remove reference to inetd startup, it is not recommended

This commit is contained in:
Andrew Bartlett 2012-09-14 23:08:53 -07:00
parent 64e3f1c637
commit 27359acf59

View File

@ -267,82 +267,7 @@ gpg: BAD signature from <quote>Samba Distribution Verification Key</quote>
</para>
<sect2>
<title>Starting from inetd.conf</title>
<indexterm><primary>inetd</primary></indexterm>
<note>
<para>The following will be different if
you use NIS, NIS+, or LDAP to distribute services maps.</para>
</note>
<para>Look at your <filename>/etc/services</filename>.
What is defined at port 139/tcp? If nothing is defined,
then add a line like this:</para>
<para><programlisting>netbios-ssn 139/tcp</programlisting></para>
<para>Similarly for 137/udp, you should have an entry like:</para>
<para><programlisting>netbios-ns 137/udp</programlisting></para>
<para>
Next, edit your <filename>/etc/inetd.conf</filename> and add two lines like this:
<programlisting>
netbios-ssn stream tcp nowait root /usr/local/samba/sbin/smbd smbd
netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
</programlisting>
</para>
<indexterm><primary>/etc/inetd.conf</primary></indexterm>
<para>
The exact syntax of <filename>/etc/inetd.conf</filename>
varies between UNIXes. Look at the other entries in inetd.conf
for a guide.
</para>
<para>
<indexterm><primary>xinetd</primary></indexterm>
Some distributions use xinetd instead of inetd. Consult the
xinetd manual for configuration information.
</para>
<note><para>Some UNIXes already have entries like netbios_ns
(note the underscore) in <filename>/etc/services</filename>.
You must edit <filename>/etc/services</filename> or
<filename>/etc/inetd.conf</filename> to make them consistent.
</para></note>
<note><para>
<indexterm><primary>ifconfig</primary></indexterm>
On many systems you may need to use the
<smbconfoption name="interfaces"/> option in &smb.conf; to specify
the IP address and netmask of your interfaces. Run
<application>ifconfig</application> as root if you do
not know what the broadcast is for your net. &nmbd; tries
to determine it at runtime, but fails on some UNIXes.
</para></note>
<warning><para>
Many UNIXes only accept around five parameters on the command
line in <filename>inetd.conf</filename>. This means you shouldn't
use spaces between the options and arguments, or you should use
a script and start the script from <command>inetd</command>.
</para></warning>
<para>
Restart <application>inetd</application>, perhaps just send it a HUP,
like this:
<indexterm><primary>killall</primary></indexterm>
<screen>
&rootprompt;<userinput>killall -HUP inetd</userinput>
</screen>
</para>
</sect2>
<sect2>
<title>Alternative: Starting &smbd; as a Daemon</title>
<title>Starting &smbd; as a Daemon</title>
<para>
<indexterm><primary>daemon</primary></indexterm>