From 46b6b8fe066a1a781692996f2e33db648f1bf1cb Mon Sep 17 00:00:00 2001 From: Chern Lee Date: Wed, 8 Aug 2001 18:44:56 +0000 Subject: [PATCH] * procces -> process * Link text of redundant "Send HUP to inetd" back to previous example Reviewed by: murray --- .../handbook/advanced-networking/chapter.sgml | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml index 7b152aab93..767f4c8e22 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -1,7 +1,7 @@ @@ -4279,7 +4279,7 @@ natd_flags="" /etc/inetd.conf, inetd can be forced to re-read its configuration file by sending a HangUP signal to the - inetd procces as shown:. + inetd process as shown: Sending <application>inetd</application> a HangUP signal @@ -4484,12 +4484,11 @@ server-program-arguments of inetd's daemons may be enabled by default. If there is no apparent need for a particular daemon, disable it! Place a # in front of the daemon in - question, and send a kill -HUP `cat - /var/run/inetd.pid` to - inetd. Some daemons, such as - fingerd, may not be desired at all - because it provides an attacker with too much - information. + question, and send a hangup signal + to inetd. + Some daemons, such as fingerd, may + not be desired at all because they provide an attacker with too + much information. Some daemons are not security-concious and have long, or non-existent timeouts for connection attempts. This allows an