Now, to get back to the original topic... John Nichel said: [snip] > No, they don't work just fine. Maybe in your production enviroment, or > in the mirror's production enviroment they work just fine, but not in > all enviroments. So likewise, your environment may require rebuilding PHP and apache from source, but not everyone's does. > Like I've stated, the problem isn't with PHP vs. > Apache 2 per se, the problem is with Apache 2's multi-threading and > third party modules included with PHP. FC ships with HTTPd configured for the "prefork" model for that reason. > You (and the mirrors) may not be > using one of the modules that have problems. With PHP being user > configurable to include/remove so many different modules, you may have a > base install working fine on one box, but then you want to play around > with the gd libraries, so you configure PHP with gd, and all of a > sudden, Apache 2 starts barffing. And since FC1 doesn't ship with these questionable modules, your recommendation to the user having an issue to "Install from source, not RPM's. Read the PHP recomendation about NOT using Apache2 and PHP together." is based on what? To sum it up, if you would have said "Some PHP modules that don't come with FC might have issues with Apache 2, are you using those" I wouldn't have had an issue. To just tell anyone that has any kind of issue "Don't use Apache 2 and PHP together, build from source" doesn't help anyone. -- William Hooper
