From owner-freebsd-questions Wed Jul 14 22: 2: 8 1999 Delivered-To: freebsd-questions@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 1294C154DB for ; Wed, 14 Jul 1999 22:02:04 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id HAA07533; Thu, 15 Jul 1999 07:02:03 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id HAA23898; Thu, 15 Jul 1999 07:02:02 +0200 (MET DST) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id HAA03402; Thu, 15 Jul 1999 07:04:21 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id FAA05188; Thu, 15 Jul 1999 05:04:21 GMT (envelope-from ust) Date: Thu, 15 Jul 1999 07:04:21 +0200 From: Udo Schweigert To: "T. William Wells" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 3.2 hosts.allow Problems Message-ID: <19990715070421.A5157@alaska.cert.siemens.de> References: <378CFDFC.16B891CC@cswnet.com> <7mj7en$k45$1@twwells.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <7mj7en$k45$1@twwells.com>; from T. William Wells on Wed, Jul 14, 1999 at 07:48:01PM -0400 X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 14, 1999 at 07:48:01PM -0400, T. William Wells wrote: > In article , > Doug 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. > No, that's not true. I never restarted inetd to enable changes in hosts.allow. (Only changes in inetd.conf have to be signald via kill -HUP, but that's a different thing). Regards ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 48000 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message