Restarting Apache without killing active connections
Changes to Apache web server’s configuration typically warrant a necessary immediate restart of the Apache. This is necessary in order for the new configuration changes to take effect due to the way Apace loads configuration settings at start-up.
Examples of changes which would warrant a restart in order to take immediate effect would be changing (adding or removing) an IP address, modifying the maximum connections limit, installing or uninstalling module files, changing virtual host configurations, and the list goes on, etc.
What is a Graceful Restart, and Why Bother Restarting Apache Gracefully?
Chances are you are already aware that the above situations would require a restart of Apache. The question that needs to be answered is “Why restart with the graceful command rather than the standard restart command. Continue Reading

