Topic awaiting preservation: Apache 2.0 httpd.conf restarting...

Why is it that every time I want to make a change to the configuation file (httpd.conf) in Apache 2.0 the changes will only take place after I reboot my computer? I restart apache and the changes don't take place, I don't understand it.

Thanks,



- Face the Present
- AIM: MASKKKK

01001101011000010111001101101011011010110110101101101011

I suppose we're talking windows here...
so, are you really starting/stopping the service?
or just restarting the front end?
(if the later, have a look at your control panel.)

No we're talking about linux...
(Which I know little about...)



- Face the Present
- AIM: MASKKKK

01001101011000010111001101101011011010110110101101101011

And why is it that sometimes when I bring up Apache it gives me that dumb screen about...you just installed Apache and other times it gives me the contents of my directory!!!! It doesn't make any sense!

Does this have anything to do with it?

Sometimes I start it with:

apachectl start

and other times I start it with

httpd -k start

Or use the same thing to stop it.



- Face the Present
- AIM: MASKKKK

01001101011000010111001101101011011010110110101101101011

You can restart Apache with:

apachectl graceful

Hi! I just put SuSE 8.0 and Apache on my computer (I've had apache working on my windows system) and I can say that at times it's quite confusing where exactly apache is getting its confiruation from (at least to a novice like myself!) Do you have the httpd daemon(sp?) starting as a "service" in the linux kernel? I got mine setup that way and it starts automatically (reading the httpd.conf file in /etc/httpd/ ) regardles of who is signed on as the user.

Actually it's even slightly more complicated than that. My Windows web site is on a seperate drive, and I wanted any visitor to see the same site regardless of the OS I was using -- I have configured SuSE to automount the other hard drive then the Apache server starts.

I haven't had any trouble getting apachectl to start, stop, or restart when logged in as ROOT but that control does NOT work as a normal user; the same can be said for making changes in the httpd.conf -- you can't do it as a normal user! (by the way, Apache in Widows does not seem to have this distinction)

My suggestion --- make your Apache configuration changes as ROOT

of course you can't restart apache or change the configuration as a normal user!

Where would you be if every john doe with a bounce shell for irc on a system could kill the webserver?!?

Now, you can archive the same level of security on windows, though it takes a bit of work.

I don't know if you've got the problem solved yet, but usually, all I have to do after editing the httpd.conf is restart the httpd daemon with:

pkill -HUP httpd

This should do the job. Then just run the following to check if the httpd daemon is running:

ps -ef