* procces -> process

* Link text of redundant "Send HUP to inetd" back to previous example

Reviewed by:	murray
This commit is contained in:
Chern Lee 2001-08-08 18:44:56 +00:00
parent 7e14cb00aa
commit 46b6b8fe06
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10254

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.71 2001/08/07 23:58:38 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.72 2001/08/08 17:35:54 dd Exp $
-->
<chapter id="advanced-networking">
@ -4279,7 +4279,7 @@ natd_flags=""</programlisting>
<filename>/etc/inetd.conf</filename>,
<application>inetd</application> can be forced to re-read its
configuration file by sending a HangUP signal to the
<application>inetd</application> procces as shown:.</para>
<application>inetd</application> process as shown:</para>
<example id="inetd-hangup">
<title>Sending <application>inetd</application> a HangUP signal</title>
@ -4484,12 +4484,11 @@ server-program-arguments</programlisting>
of <application>inetd</application>'s daemons may be enabled by
default. If there is no apparent need for a particular daemon,
disable it! Place a <quote>#</quote> in front of the daemon in
question, and send a <command>kill -HUP `cat
/var/run/inetd.pid`</command> to
<application>inetd</application>. Some daemons, such as
<application>fingerd</application>, may not be desired at all
because it provides an attacker with too much
information.</para>
question, and send a <link linkend="inetd-hangup">hangup signal
to inetd</link>.
Some daemons, such as <application>fingerd</application>, may
not be desired at all because they provide an attacker with too
much information.</para>
<para>Some daemons are not security-concious and have long, or
non-existent timeouts for connection attempts. This allows an