Stable x86 just got a new apache server, and it's puzzling me. For one thing, /etc/conf.d/apache2 now ends with this
# Environment variables to keep # All environment variables are cleared from apache # Use this to preserve some of them # NOTE!!! It's very important that this contains PATH # TODO: Phase this out in favor of /etc/conf.d/env_whitelist #KEEPENV="PATH" It has said all along that it's important to have PATH, but now it's commented out without any replacement in env_whitelist. Moreover, there's no example in env_whitelist to show the syntax. I just put PATH in there on a line of its own, and hoped for the best. The bigger puzzle is this one: I can't stop apache because it can't be found, but I also can't start it because it's already running. It is in fact running and serving web pages. But I'd like the init stuff to be a lot more consistent. The confusion about cupsd and vmware is a separate issue I've been meaning to ask about for months; I don't think it has anything to do with apache2. treat ~ # cd /etc/init.d treat init.d # ./apache2 stop * Stopping apache2 ... No /usr/sbin/apache2 found running; none killed. [ !! ] treat init.d # ./apache2 start * WARNING: apache2 has already been started. treat init.d # ./apache2 status * Caching service dependencies ... * Service 'cupsd' should be AFTER service 'vmware', but one of * the services 'vmware' depends on, depends on 'cupsd'! [ ok ] * status: started treat init.d # -- Kevin O'Gorman, PhD
