From owner-freebsd-hackers Mon Jun 21 2:28:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 7B06114DDD; Mon, 21 Jun 1999 02:28:07 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10w0Mo-000KnL-00; Mon, 21 Jun 1999 11:27:50 +0200 From: Sheldon Hearn To: Aaron Smith Cc: freebsd-hackers@freebsd.org, wietse@freebsd.org Subject: Re: inetd/tcpd...changing hosts.allow...plus a documentation issue In-reply-to: Your message of "Sun, 20 Jun 1999 17:49:59 MST." <199906210049.RAA01387@sigma.veritas.com> Date: Mon, 21 Jun 1999 11:27:49 +0200 Message-ID: <79938.929957269@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Jun 1999 17:49:59 MST, Aaron Smith wrote: > unfortunately incoming telnet was still denied. at first i tried > HUPping inetd to reread the hosts.allow, but after looking at the > source it appears to re-read its information each time hosts_access is > called. has anyone else had problems updating this file and getting > inetd to reflect the new behavior? Inetd reads inetd.conf on startup and on SIGHUP. The hosts_access() check checks the hosts.allow file on each call. > i'm looking at it a bit but perhaps a maintainer knows if something is > being cached here? The bug that caused inetd to corrupt config on SIGHUP was fixed in rev 1.50 of inetd.c, which has not yet been merged to STABLE. In STABLE, LIBWRAP_INTERNAL is not default yet. In CURRENT, it is. You can expect the internal wrapping fixes and the SIGHUP bugfix to be merged back to STABLE soon (within a week). I'm in no rush, and I'm glad I didn't rush, since David Malone has already uncovered a bug in the handling of maxchild, which I believe is worth fixing before the merge. :-) Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message