From owner-freebsd-stable  Thu Jul 20  0:15:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62])
	by hub.freebsd.org (Postfix) with ESMTP id 2E94437B840
	for <freebsd-stable@FreeBSD.ORG>; Thu, 20 Jul 2000 00:15:11 -0700 (PDT)
	(envelope-from DougB@gorean.org)
Received: from gorean.org (master [10.0.0.2])
	by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA06236;
	Thu, 20 Jul 2000 00:15:05 -0700 (PDT)
	(envelope-from DougB@gorean.org)
Message-ID: <3976A6F9.111C93FA@gorean.org>
Date: Thu, 20 Jul 2000 00:15:05 -0700
From: Doug Barton <DougB@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Eric D. Futch" <efutch@nyct.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: hosts.allow strangeness?
References: <Pine.BSF.4.21.0007181817070.27653-100000@bsd1.nyct.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Eric D. Futch" wrote:
> 
> Ok never mind :)  Forgot to add -w to inetd when I killed/restarted it.

	If you change inetd.conf you need to -HUP inetd, or kill it and restart
it. You don't need to do either if you just change hosts.allow. The next
time someone tries to connect to your machine the conf file will be read
again. 

HTH,

Doug


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