Mutex directive: finish support of DefaultRuntimeDir a partial conversion was made in r1299718, but I'm not sure when that change is effective

Move away from DEFAULT_REL_RUNTIMEDIR and use ap_runtime_dir_relative() API

Add lots of unique tags to error log messages

Add -D DUMP_RUN_CFG option to dump some configuration items from the parsed (or default) config. This is useful for init scripts that need to setup temporary directories and permissions, for example if those temporary directories are located on a ram disk.

Cleanup effort in prep for GA push: Trim trailing whitespace... no func change

Introduce ap_(get|set)_core_module_config() functions/macros and use them everywhere. We know that the core module has module_index 0. Therefore we can save some pointer operations in ap_get_module_config(cv, &core_module) and ap_set_module_config(cv, &core_module, val). As these are called rather often, this may actually have some (small) measurable effect.

hide some unused code on Win32 and NetWare

enable DEFAULT_REL_RUNTIMEDIR on NetWare and Windows this commit is missing the Windows and NetWare build logic to copy the appropriate file to include/ap_config_layout.h

Add a generic pool cleanup function that sets a pointer to NULL and use it to replace various pool cleanup functions.

Use the new APLOG_USE_MODULE/AP_DECLARE_MODULE macros everywhere to take advantage of per-module loglevels

It is not inconvenient to return the derived filename here, let's save the caller later hassle in looking this up, if they like.

Fix startup segfault when the Mutex directive is used but no loaded modules use httpd mutexes. Add an init call from core's pre-config hook to ensure init is performed before the config is parsed. PR: 48787

string constness

fix this: util_mutex.c: In function ‘ap_set_mutex’: util_mutex.c:188: warning: comparison between pointer and integer util_mutex.c:174: warning: unused variable ‘type’

Add OmitPID keyword on Mutex directive to suppress the addition of the parent pid to the generated lock file name. Change the Mutex directive syntax from Mutex default|mutex-name mechanism to Mutex mechanism [default|mutex-name] ... [OmitPID] as suggested by wrowe. (Thanks!)

fix the "fix" in r883816 internal function ap_set_mutex() should be AP_DECLARE_NONSTD() like our other directive parsers

fix Win32 compile failure in r883540, reported by Gregg Smith DEFAULT_REL_RUNTIMEDIR defined only in mpm_default.h for NetWare and dsp-based Win32 builds mpm_default.h not in normal include path on Unix thus, hardcode "logs" directory when DEFAULT_REL_RUNTIMEDIR isn't defined (file-based mutexes aren't configurable for those platforms anyway)

fix Win32 compile failure in r883540, reported by Gregg Smith (on Win32, external APIs use one calling convention while directive parsers use a different one)

fix Win32 compile failure in r883540, reported by Gregg Smith

Replace AcceptMutex, LockFile, RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath with a single Mutex directive. Add APIs to simplify setup and user customization of APR proc and global mutexes. (See util_mutex.h.) Build-time setting DEFAULT_LOCKFILE is no longer respected; set DEFAULT_REL_RUNTIMEDIR instead. Some existing modules, such as mod_ldap and mod_auth_digest gain configurability for their mutexes.

remove leader, perchild, and threadpool MPMs (other than non-English bits in common parts of the manual)

Remove all references to CORE_PRIVATE.

ap_available_mutexes_string and ap_add_available_mutexes_string cannot be data symbols when mod_ssl is built as a loadable module; using an external string constant in a loadable module is not portable. Also reorganize file and sem to follow their explicit mechanisms, and ensured that the explicit mechansims are listed in order of preference. This raises a question, would [fcntl|file] be a clearer way of indiciating what the file/sem methods devolve to?

Minor quibble; the declarespec for data comes after the data type.

Once SSLMutex allowed for the setting of both the locking method and the lockfile location, I never liked how AcceptMutex was linked to LockFile. This seemed unnecessary. Much better to have AcceptMutex do both as well. Plus, now that we will likely see other modules require a "standard" way of setting mutexes, why not have Apache provide that as an API of sorts. Anyway, LockFile is now depreciated and AcceptMutex is now SSLMutex-like. We also provide a short function that "parses" out a mutex parameter and strips out the mechanism and lockfile location. AcceptMutex and SSLMutex is this capability.