txt 6http://apr.apache.org/ 1.3. OVERVIEW OF NEW FEATURES IN APACHE HTTP SERVER 2.2 15 Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular Stopping and Restarting (p. 29) Overview for the impatient Installing on Fedora/CentOS/Red Hat Enterprise Linux sudo yum install httpd sudo systemctl enable httpd sudo systemctl start httpd ! Newer releases AND RESTARTING APACHE HTTP SERVER 31 listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout

| Glossary | Sitemap ap_register_output_filter_protocol or ap_filter_protocol calls. Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular httpd Stopping and Restarting Overview for the impatient Installing on Fedora/CentOS/Red Hat Enterprise Linux sudo yum install httpd sudo systemctl enable httpd sudo systemctl start httpd Newer releases will then remove its PidFile and cease listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout

| Glossary | Sitemap ap_register_output_filter_protocol or ap_filter_protocol calls. Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular will then remove its PidFile and cease listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout request ID will be used as the log entry ID, too. During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can accomplish this using: tail -f error_log

| Glossary | Sitemap ap_register_output_filter_protocol or ap_filter_protocol calls. Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular will then remove its PidFile and cease listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout request ID will be used as the log entry ID, too. During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can accomplish this using: tail -f error_log

| Glossary | Sitemap ap_register_output_filter_protocol or ap_filter_protocol calls. Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular will then remove its PidFile and cease listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout request ID will be used as the log entry ID, too. During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can accomplish this using: tail -f error_log

txt 6http://apr.apache.org/ 1.3. OVERVIEW OF NEW FEATURES IN APACHE HTTP SERVER 2.2 15 Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular AND RESTARTING APACHE HTTP SERVER 31 listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout request ID will be used as the log entry ID, too. During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can accomplish this using: tail -f error log

| Glossary | Sitemap ap_register_output_filter_protocol or ap_filter_protocol calls. Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular will then remove its PidFile and cease listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout request ID will be used as the log entry ID, too. During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can accomplish this using: tail -f error_log

txt 6http://apr.apache.org/ 1.3. OVERVIEW OF NEW FEATURES IN APACHE HTTP SERVER 2.2 13 Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular AND RESTARTING APACHE HTTP SERVER 29 listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout request ID will be used as the log entry ID, too. During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can accomplish this using: tail -f error log

txt 6http://apr.apache.org/ 1.3. OVERVIEW OF NEW FEATURES IN APACHE HTTP SERVER 2.2 13 Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular AND RESTARTING APACHE HTTP SERVER 29 listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout request ID will be used as the log entry ID, too. During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can accomplish this using: tail -f error log

| Glossary | Sitemap ap_register_output_filter_protocol or ap_filter_protocol calls. Monitor hook added Monitor hook enables modules to run regular/scheduled jobs in the parent (root) process. Regular will then remove its PidFile and cease listening on all ports. The parent will continue to run, and monitor children which are handling requests. Once all children have finalised and exited or the timeout request ID will be used as the log entry ID, too. During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can accomplish this using: tail -f error_log