From c31aede2e10c480b5bf37f8e2467c91213699849 Mon Sep 17 00:00:00 2001
From: Colm MacCarthaigh
Date: Sun, 28 Aug 2005 10:48:09 +0000
Subject: [PATCH] Add a note on the possible pit-falls that lie ahead when
running multiple instances of httpd at the same time.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@263857 13f79535-47bb-0310-9956-ffa450edef68
---
docs/manual/stopping.xml | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/docs/manual/stopping.xml b/docs/manual/stopping.xml
index d3798f65d8..87643307cd 100644
--- a/docs/manual/stopping.xml
+++ b/docs/manual/stopping.xml
@@ -203,6 +203,25 @@ error. See above for a method of avoiding this.
as the PidFile will
have been removed, you will not be able to use
apachectl
or httpd
to send this signal,
+
+ The graceful-stop
signal allows you to run multiple
+ identically configured instances of httpd at the
+ same time. This is a powerful feature when performing graceful
+ upgrades of Apache, however it can also cause deadlocks and race
+ conditions with some configurations.
+
+ Care has been taken to ensure that on-disk files
+ such as the Lockfile and ScriptSock files contain the server
+ PID, and should co-exist without problem. However, if a configuration
+ directive, third-party module or persistent CGI utilises any other on-disk
+ lock or state files; care should be taken to ensure that multiple running
+ instances of httpd do not clobber each others files.
+
+ You should also be wary of other potential race conditions, such as
+ using rotatelogs style piped logging. Multiple running
+ instances of rotatelogs attempting to rotate the same
+ logfiles at the same time may destroy each other's logfiles.
--
2.40.0