On Fri, 2 Jun 2000, DCR wrote:
Okay I am sure you can all do this,
But i am darned if I can get apache up and running
There seems to be so much conflicting advice Do I get rid of srm.conf and access.conf and just use httpd.conf do I keep all three Why is it that after setting the servername and document root, netscape keeps trying to access / instead of my document root ???
Help !!!!!
----------
Under SuSE Apache runs out of the box - all you have to do is enable it using yast (or directly). I assume that you want to modify the standard configuration. To keep things easy keep all three conf files and only modify those you have to. What do you need to change from the standard config? I don't know if I am being too simplistic here but have you restarted httpd after modifying the conf files (eg. kill -HUP <pid> )? ____________________________________ Giles Nunn - Network Manager Carms Schools ICT Development Centre Tel: +44 01239 710662 Fax: 710985 ____________________________________
On Fri, 2 Jun 2000, Giles Nunn wrote:
Do I get rid of srm.conf and access.conf and just use httpd.conf do I keep all three
access.conf and srm.conf are supported in order to allow backwards compatibility with NCSA httpd (basically the original web server). They are no longer required, and best practice seems to be to keep everything together in httpd.conf.
Why is it that after setting the servername and document root, netscape keeps trying to access / instead of my document root ???
Sounds like a restart of the server is required.
I don't know if I am being too simplistic here but have you restarted httpd after modifying the conf files (eg. kill -HUP <pid> )?
The correct way is to run "apachectl restart", or "apachectl graceful" if you want to restart each task once its finished serving its current connection (this avoids cutting people off mid-page). -- ___ _ In a world without fences - who needs Gates? | (_' M1CHW ._|on ._)tockill <jon@ops-wing.demon.co.uk>
participants (2)
-
Giles Nunn -
Jon Stockill