• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Apache reload after config change"

Collapse

  • NoddY
    replied
    Did you know the name Apache came from "a patchy sever".

    Just thought you'd all like to know that one.

    Leave a comment:


  • AtW
    replied
    The last one is not present on Win NT build of apache

    I think I will have separate code paths though.

    Leave a comment:


  • TheMonkey
    replied
    Or:

    apachectl graceful

    Leave a comment:


  • AtW
    replied
    Now that's better, thanks!

    Leave a comment:


  • Ardesco
    replied
    Ok i'm talking utter tulipe. Try:

    /etc/init.d/apache2 reload

    Leave a comment:


  • AtW
    replied
    This does not sound right - surely a big web farm with lots of virtual sites hosted would have to restart all apache childs just because they added new site?

    Leave a comment:


  • Ardesco
    replied
    i'm afraid its an /etc/init.d/apache2 restart all the way

    Leave a comment:


  • AtW
    started a topic Apache reload after config change

    Apache reload after config change

    Is there a better way to make Apache take into account changes made to httpd.conf than stupidly stopping and starting it again? I want to make change to config and then make apache reload it nicely without interrupting work.

    Something tells me that this would be too good to be true...

Working...
X