From 993bb3331a34ecd013a1b68b7c5e299866fd9b4a Mon Sep 17 00:00:00 2001 From: Joe Orton Date: Jul 10 2019 07:41:43 +0000 Subject: Updates for current httpd best practice in Fedora. --- diff --git a/modules/system-administrators-guide/pages/_partials/servers/The_Apache_HTTP_Server.adoc b/modules/system-administrators-guide/pages/_partials/servers/The_Apache_HTTP_Server.adoc index 2fc2b07..f051d86 100644 --- a/modules/system-administrators-guide/pages/_partials/servers/The_Apache_HTTP_Server.adoc +++ b/modules/system-administrators-guide/pages/_partials/servers/The_Apache_HTTP_Server.adoc @@ -24,7 +24,7 @@ is replaced by [subs="quotes"] ---- -apachectl graceful +systemctl reload httpd ---- The `systemd` unit file for `httpd` has different behavior from the init script as follows: @@ -91,8 +91,6 @@ Removed modules:: List of `httpd` modules removed in {MAJOROSVER}: mod_auth_mysql, mod_auth_pgsql::: [application]*httpd 2.4* provides SQL database authentication support internally in the [application]*mod_authn_dbd* module. -mod_perl::: [application]*mod_perl* is not officially supported with [application]*httpd 2.4* by upstream. - mod_authz_ldap::: [application]*httpd 2.4* provides LDAP support in sub-package [package]*mod_ldap* using [application]*mod_authnz_ldap*. [[s2-apache-version2-migrating]] @@ -191,23 +189,22 @@ There are three different ways to restart a running `httpd` service: This stops the running `httpd` service and immediately starts it again. Use this command after installing or removing a dynamically loaded module such as PHP. -. To only reload the configuration, as `root`, type: +. To only reload the configuration without interrupting active requests, as `root`, type: [subs="attributes"] ---- ~]#{nbsp}systemctl reload httpd.service ---- -This causes the running `httpd` service to reload its configuration file. Any requests currently being processed will be interrupted, which may cause a client browser to display an error message or render a partial page. +This causes the running `httpd` service to reload its configuration file. Any requests currently being processed will not be interrupted, so configuration changes will only take effect for new client connections. -. To reload the configuration without affecting active requests, enter the following command as `root`: +. To reload the configuration and immediately terminate any active connections, enter the following command as `root`: [subs="attributes"] ---- -~]#{nbsp}apachectl graceful +~]#{nbsp}systemctl kill --kill-who=main --signal=HUP httpd ---- -This causes the running `httpd` service to reload its configuration file. Any requests currently being processed will continue to use the old configuration. [[s3-apache-running-status]] ==== Verifying the Service Status