RE: Weird problem with httpd.conf save

["David Kazias" <david@xxxxxxxxxxxxxxx>]

> I almost positively absolutely believe that just copying Apache's conf
file
> has no effect on the web server.

To the best of my knowledge, this is correct. HTTP.conf is loaded at
startup, then never looked at again outside a restart/start/graceful.

> My best guess is the httpd.conf file was edited and errors were introduced
> and apache was NOT restarted. Later (possibly much later) our unsuspecting
> web server admin copied the file and THEN restarted apache.

The best way to do this is to make changes direct to the HTTP.conf file
using vi/BBEdit/etc, while the iTools Admin server is running. Then, someone
makes changes within the iTools admin without stopping and restarting it and
the previous changes get tossed. Why? Because, like Apache, the iTools admin
server loads all the conf files at start up and works with them from memory
from that point out.

For this reason, it's generally best practice to make sure the Admin Server
is shut down before you tweak the http.conf file, or at least stop/restart
it afterwards.

David Kazias
Eternity Web Designs Inc.


---------
Tenon Intersystems' iTools Mailing List
To unsubscribe: send mail to 
itools-request@xxxxxxxxxxxxxxx
with the body only containing: 
unsubscribe
Find the searchable mailing list archives 
at:
http://itools.blackpepper.co.nz/