From owner-freebsd-current Mon Jun 7 16:39:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 9760915857 for ; Mon, 7 Jun 1999 16:39:11 -0700 (PDT) (envelope-from a.reilly@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id JAA21994 for ; Tue, 8 Jun 1999 09:39:09 +1000 (EST) X-BPC-Relay-Envelope-From: a.reilly@lake.com.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-48-172.nsw.bigpond.net.au [24.192.48.172]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id JAA24011 for ; Tue, 8 Jun 1999 09:39:07 +1000 (EST) Received: (qmail 85299 invoked by uid 1000); 7 Jun 1999 23:39:07 -0000 From: "Andrew Reilly" Date: Tue, 8 Jun 1999 09:39:07 +1000 To: Dom Mitchell Cc: Ben Rosengart , current@FreeBSD.ORG Subject: Re: tcp_wrapper in contrib and ports? Message-ID: <19990608093907.A85247@gurney.reilly.home> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dom Mitchell on Mon, Jun 07, 1999 at 04:34:53PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 07, 1999 at 04:34:53PM +0100, Dom Mitchell wrote: > On 7 June 1999, Ben Rosengart proclaimed: > > I am curious as to why tcp_wrappers are present in /usr/src/contrib as > > well as in the ports collection. Can someone please enlighten me? TIA. > > To support 2.2.x users? Maybe 3.x users actually want tcpd too. I'm running -STABLE, and qmail, and discovered that tcp_wrappers was somehow part of the system when things started misbehaving. Oddly, tcpd itself is _not_ built by the system, it seems. The libwrap that is built (or at least the man page for tcpdchk) seems to think that the control files hosts.access and hosts.deny still live in /usr/local/etc/, rather than where you would expect a system component to put them: /etc. My current source of confusion is with the tcpd from ports, which doesn't mention what level it is syslogging at: I can't find any of it's log messages... -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message