file defined by the optional <var>/path/to/lockfile</var>
parameter. One can also use the <directive module="mpm_common"
>LockFile</directive> directive to specify the lockfile,
- although this is depreciated.</dd>
+ although this is deprecated.</dd>
<dt><code>fcntl<<var>:/path/to/lockfile</var>></code></dt>
<dd>uses the <code>fcntl(2)</code> system call to lock the
file defined by the optional <var>/path/to/lockfile</var>
parameter. One can also use the <directive module="mpm_common"
>LockFile</directive> directive to specify the lockfile,
- although this is depreciated.</dd>
+ although this is deprecated.</dd>
<dt><code>file<<var>:/path/to/lockfile</var>></code></dt>
<dd>This directive tells Apache to pick the "best" file locking
<directivesynopsis>
<name>LockFile</name>
-<description>Location of the accept serialization lock file <em>(depreciated)</em></description>
+<description>Location of the accept serialization lock file <em>(deprecated)</em></description>
<syntax>LockFile <var>filename</var></syntax>
<default>LockFile logs/accept.lock</default>
<contextlist><context>server config</context></contextlist>
creating a lockfile with the same name as the one the server will try
to create.</p>
</note>
- <note type="warning"><title>Depreciated</title>
- <p>This directive is depreciated. It is strongly suggested that
+ <note type="warning"><title>Deprecated</title>
+ <p>This directive is deprecated. It is strongly suggested that
you use <directive module="mpm_common">AcceptMutex</directive> to
specify both the mutex locking implementation as well as
the lockfile location.</p>
#endif
#ifdef AP_MPM_WANT_SET_LOCKFILE
AP_INIT_TAKE1("LockFile", ap_mpm_set_lockfile, NULL, RSRC_CONF,
- "The lockfile used when Apache needs to lock the accept() call (depreciated)"),
+ "The lockfile used when Apache needs to lock the accept() call (deprecated)"),
#endif
#ifdef AP_MPM_WANT_SET_MAX_REQUESTS
AP_INIT_TAKE1("MaxRequestsPerChild", ap_mpm_set_max_requests, NULL, RSRC_CONF,