From owner-freebsd-questions Wed Apr 26 20:58:22 2000 Delivered-To: freebsd-questions@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 1609937BDBB for ; Wed, 26 Apr 2000 20:58:19 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id A2FAAA838; Thu, 27 Apr 2000 13:58:45 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id A0BC5540E; Thu, 27 Apr 2000 13:58:45 +1000 (EST) Date: Thu, 27 Apr 2000 13:58:45 +1000 (EST) From: andrew@ugh.net.au To: "James B. Huber" Cc: Tobias Roth , questions@FreeBSD.ORG Subject: Re: tcpd in 4.0-stable In-Reply-To: <200004261254.IAA19942@moses.gencon.com> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000, James B. Huber wrote: > tcpd itself is not actually on my system anywhere. > In fact the only "source" for it is in /usr/src/contrib/tcp_wrappers/tcpd.c > and make buildworld didn't compile it, and it make installworld didn't > attempt to install it (or compile it either). The idea is that tcpd's functionality is built into the system. inetd performs wrapping without calling tcpd as long as it is run with the -wW flags. Are you wanting tcpd for something other than use with inetd? Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message