Date: Sun, 24 Sep 1995 19:34:24 -0700 (PDT) From: Tom Samplonius <tom@uniserve.com> To: John Fieber <jfieber@indiana.edu> Cc: Paul Traina <pst@freefall.freebsd.org>, CVS-commiters@freefall.freebsd.org, cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: ports/net/apache/scripts configure Message-ID: <Pine.BSF.3.91.950924192801.1217C-100000@haven.uniserve.com> In-Reply-To: <Pine.BSF.3.91.950924210229.333D-100000@fieber-john.campusview.indiana.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 24 Sep 1995, John Fieber wrote: > On Sun, 24 Sep 1995, Tom Samplonius wrote: > > > On Sun, 24 Sep 1995, John Fieber wrote: > > > > > 1) Can we install the binary as /usr/local/libexec/httpd? > > > > Surely you mean /usr/local/sbin/httpd? > > No I didn't, but I can think of some good arguments for putting it > there. > > man hier says: > > libexec/ system daemons & system utilities (executed by other > programs) > > ... > > sbin/ system daemons & system utilities (executed by users) > > so it really depends on whether you view it as something that users use > on their own, or something that is started at boot (or via inetd) that users > can use via their ~/public_html directories. > > Anybody with strong feelings either way? Regardless, I definately think > that /usr/local/www/httpd is *not* the place for it. Things started at boot should be in /usr/local/sbin too. /usr/local/libexec should be reserverd for executables that are not stand alone. This keeps things nice, because /usr/local/sbin should be in root's and other admin users PATH, while it shouldn't make sense to directly run anything in libexec. You are right though, /usr/local/www/httpd is not right. Although samaba installs itself in /usr/local/samba/bin these days, which is also very odd. Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.950924192801.1217C-100000>