From owner-freebsd-questions  Wed Jul 14 16:50: 8 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from twwells.com (twwells.com [209.118.236.57])
	by hub.freebsd.org (Postfix) with SMTP id 3216515402
	for <freebsd-questions@freebsd.org>; Wed, 14 Jul 1999 16:50:06 -0700 (PDT)
	(envelope-from news@twwells.com)
Received: from news by twwells.com with local (Exim 1.71 #2)
	id 114Ykr-0005QG-00; Wed, 14 Jul 1999 19:48:01 -0400
From: bill@twwells.com (T. William Wells)
To: freebsd-questions@freebsd.org
Subject: Re: 3.2 hosts.allow Problems
Message-ID: <7mj7en$k45$1@twwells.com>
References: <378CFDFC.16B891CC@cswnet.com> <Pine.BSF.4.05.9907141509360.29705-100000@dt054n86.san.rr.com>
Date: Wed, 14 Jul 1999 19:48:01 -0400
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <Pine.BSF.4.05.9907141509360.29705-100000@dt054n86.san.rr.com>,
Doug  <Doug@gorean.org> wrote:
: > Now nothing is being denied.  To restart inetd, I am using "killall
: > inetd;inetd".
:
:       First, you shouldn't have to start inetd for changes in
: hosts.allow to take effect.

"Shouldn't" is correct. Unfortunately, reality doesn't conform. In
my experience, you have to kill (SIGTERM) inetd and restart it in
order for hosts.allow changes to take effect.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message