> 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.
I had the same problem yesterday, but rebooting the machine fixed it. As for the KEEPENV, I was puzzled by that too but I didn't add anything to env_whitelist and I left KEEPENV commented. Everything seems to be fine. Today apache2 wants to upgrade to 2.2.4-r12. I've got cold feet. Anyone tried this yet? - Grant -- [EMAIL PROTECTED] mailing list
