From owner-freebsd-commit Sun Sep 24 21:11:41 1995 Return-Path: owner-commit Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA00242 for freebsd-commit-outgoing; Sun, 24 Sep 1995 21:11:41 -0700 Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA00228 for cvs-all-outgoing; Sun, 24 Sep 1995 21:11:35 -0700 Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA00217 for cvs-ports-outgoing; Sun, 24 Sep 1995 21:11:33 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA00210 for ; Sun, 24 Sep 1995 21:11:28 -0700 Received: by haven.uniserve.com id <30987>; Sun, 24 Sep 1995 21:13:16 +0100 Date: Sun, 24 Sep 1995 21:13:11 -0700 (PDT) From: Tom Samplonius To: Paul Traina cc: John Fieber , cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: ports/net/apache/scripts configure In-Reply-To: <199509250308.UAA03880@precipice.shockwave.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-commit@FreeBSD.org Precedence: bulk On Sun, 24 Sep 1995, Paul Traina wrote: > httpd can be started by inetd (theoretically) so libexec might make more sense. > It's more friendly to tcpd if you were insane enough to build such a config. That's my point. It makes sense to run httpd as a daemon, so it should be in sbin. As for tcpd, why on earth would you want exec yet another program before httpd, when httpd has access control? If you absolutely wanted be rude and refuse TCP connections, use xinetd, at least you don't need the extra exec. Tom