On Sun, 11 Mar 2007 14:49:47, Dan Shoop wrote:
> Then perhaps you have *different* problem, namely apache won't start
not that it's not being told to start.
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.
Which is why answers like "well when apache didn't start for me it
was because there was ocelot spleen gunking my air movers, so this
must be your problem too if apache isn't starting" is so ridiculous
of an answer. I think we all know there could be oodles of reasons
why something doesn't start and correlating it to any one w/o
troubleshooting is woolly thinking.
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.
*That* problem is likely the one of trying to start two services on
the same port.
>>My server isn't used for anything important so I haven't really
looked into what's going on.
Then disregard any attempts to help. ;)
If you don't care to spend the time diagnosing your issue, why are you
telling us about it?
Because he wants someone else to do his work for him ;)
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