From what Devon has stated, it's not clear which type of problem he's
having, but I can speak from personal experience when I say it's entirely
possible that OS X is not starting apache for another reason. I inherited
a server with similar symptoms (running 10.3) and tracked it down to
having two StartupItems both claiming to provide "Web Server":
"/Sys/Lib/SI/Apache/" and "/Lib/SI/Apache2/". OS X chose to run the
Apache2 StartupItem (Apache 2 was not correctly configured) rather than
the Apache StartupItem. Once I removed Apache2, it worked just fine. I
don't know it something similar could happen with launchd.
It could have something to do with apache 2 because I did try to
install a startup item for it.
My issue is resolved since I reinstalled everything and got it
working, but I don't know about the thread starter.
If you don't care to spend the time diagnosing your issue, why are you
telling us about it?
I didn't start the thread actually someone else did, I was just
saying that Dan's suggestion isn't the only reason that it wouldn't
There are a legion of reasons why something might not start.
Permissions problems, configuration problems, resource problems,
misapplication problems, build problems, library problems, dynamic
link problems, ...
iWiring provides systems and networks support for Mac OS X, unix, and
Open Source application technologies at affordable rates.
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden