fix spelling error in comment

No need for process.h system include since we don't use getpid() any more

Axe check for second post config call. New ap_state_query(AP_SQ_MAIN_STATE) == AP_SQ_MS_CREATE_PRE_CONFIG API call does exactly that, so we were actually expecting 4 calls ending up with NULL config in child hook

Add lots of unique tags to error log messages

Remove some getpid() logging, this is now also included in the error log format.

s/WATCHODG/WATCHDOG/

solve getpid() process.h function order

Fix two bugs introduced by r1070153

Use ap_state_query() to fix many modules that were not correctly initializing if they were not active during server startup but got enabled later during a graceful restart (in which case they need to do all work during a single config run).

OS/2 build fix: Remove use of non-portable apr_get_os_error() and just return APR_ENOMEM if apr_pcalloc() returns NULL.

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

Catch up with ap_[proc|global]_mutex_create api change

tweaks to r883540: watchdog: use better mutex type name ldap/digest: use same FOO_mutex_type variable name as other modules for easier searching

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.

change the callable functions in the mod_watchdog API to optional hooks to avoid module ordering or other symbol resolution issues; affected: ap_watchdog_get_instance ap_watchdog_register_callback ap_watchdog_set_callback_interval

Here's the simpler solution to the two groups of mappers/ modules... The mod_so and mod_watchdog are truly not mappers/ at all. Very open to better names than modules/core/ but these are clearly API's which are to be consumed by the httpd core, or generically, any module.