From: Cliff Woolley Date: Tue, 2 Apr 2002 02:38:31 +0000 (+0000) Subject: Grammar police. (Well, you asked for it. ;) There's still a split X-Git-Tag: 2.0.35~72 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b43d2c5b00d55ca96225c9600274af02b9709026;p=apache Grammar police. (Well, you asked for it. ;) There's still a split infinitive in the last sentence, but I don't really believe in that rule, so... git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@94372 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mpm_common.xml b/docs/manual/mod/mpm_common.xml index 974522a6cc..ad45e0f16b 100644 --- a/docs/manual/mod/mpm_common.xml +++ b/docs/manual/mod/mpm_common.xml @@ -383,12 +383,12 @@ the child processes prefork -

Apache uses a scoreboard to communicate between its children - and the parent. Some architectures require a file to facilitate - this communication. If left unspecified, Apache first attempts to - create the scoreboard entirely in memory (using anonymous shared - memory), and failing that will attempt to create the file on disk - (using file-based shared memory). Specifying this directive causes +

Apache uses a scoreboard to communicate between its parent + and child processes. Some architectures require a file to facilitate + this communication. If the file is left unspecified, Apache first + attempts to create the scoreboard entirely in memory (using anonymous + shared memory) and, failing that, will attempt to create the file on + disk (using file-based shared memory). Specifying this directive causes Apache to always create the file on the disk.

File-based shared memory is useful for third-party applications