I have no reference to /Users/arthurpesa/public_html/ in any conf file that
I can find. I also do not have a directory under /Users/arthurpesa called
/public_html/. I have no redirect in my conf file either. I have combed
through the original conf file supplied in 1.3 and added what I felt was
nece
Arthur Pesa wrote:
> Thanks for the additional insight. I think I have gotten past the startup
> error. I cp'd /private/etc/httpd/httpd.conf to httpd.conf.bak. I then
> restarted apache and the new installation seems to work. However I have a
> couple questions.
>
> I am using the following comman
Thanks for the additional insight. I think I have gotten past the startup
error. I cp'd /private/etc/httpd/httpd.conf to httpd.conf.bak. I then
restarted apache and the new installation seems to work. However I have a
couple questions.
I am using the following command line to start the server:
ap
What is "shutting down" is the new instance, not the already-running
instance.
Try using "graceful" instead of "start"; if it is already running this
might restart it assuming they are the same program (both version 2
and not the factory installed version 1).
You might also try using the lsof com
Thanks,
I compiled and installed apache2.2.4 in usr/local/apache2 (by default). I
have disabled Web Sharing in prefs from the start. After the install and
initial start command I noticed it was using the httpd.conf file from
private/etc/httpd (this is shipped from Apple and will start apache versi
Arthur Pesa wrote:
> I have downloaded and compiled apache 2.2.4 on my Mac Powerbook G4 OS X
> 10.4.9. I did not make any significant changes to the httpd.conf file
> initially. I started the server and it error’d on startup with the
> following messages in terminal. I am not getting anything relev
I have downloaded and compiled apache 2.2.4 on my Mac Powerbook G4 OS X
10.4.9. I did not make any significant changes to the httpd.conf file
initially. I started the server and it error¹d on startup with the following
messages in terminal. I am not getting anything relevant to this error in
logs/e
