Date: Fri, 13 Jan 2006 13:15:17 -0600 From: Greg Barniskis <nalists@scls.lib.wi.us> To: Frank Staals <frankstaals@gmx.net> Cc: snarmont@wnec.edu, freebsd-questions@freebsd.org Subject: Re: httpd could not be started Message-ID: <43C7FC45.1020907@scls.lib.wi.us> In-Reply-To: <43C7F609.3010607@gmx.net> References: <17821403.1137174943074.JavaMail.root@m11> <43C7F032.3020109@scls.lib.wi.us> <43C7F609.3010607@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Frank Staals wrote: > Greg Barniskis wrote: >> apache2_enable="YES" >> >> in your rc.conf? >> >> The need for this as well as the proper syntax should be noted in the >> file /usr/ports/www/apache2/pkg-msg. For any other port you install >> there's probably gold nuggets of info in its pkg-msg file. This stuff >> displays during the make install, but then so does several K of other >> info so it's not hard to miss these things. >> > In fact, it doesn't realy matter if you add apache_enable="YES" to > rc.conf ( since het installed apache13 adding apache2_enable="YES" would > be quite useless ... ) Duh. Sorry, the later line about him trying apache22 got stuck in my mind. > when you start it manually from commandline, > adding it to rc.conf is only usefull when you want to start apache from > boot, which can be quite usefull, but it can't be the reason why apache > wouldn't start. Oh. I was sure that I'd read in a previous thread that the lack of an enable flag would stop it from being started at all, but that must have been for a different port or in a different context. Anyway, thanks for the correction, always glad to have my misconceptions destroyed. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) <gregb at scls.lib.wi.us>, (608) 266-6348
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43C7FC45.1020907>