http://httpd.apache.org/docs/current/mod/core.html#mutex claims httpd -V will print the default (optimal) Mutex for this platform, however it does not: Server version: Apache/2.4.1 (Unix) Server built: Mar 27 2012 20:35:35 Server's Module Magic Number: 20120211:0 Server loaded: APR 1.4.6, APR-UTIL 1.4.1 Compiled using: APR 1.4.6, APR-UTIL 1.4.1 Architecture: 64-bit Server MPM: event threaded: yes (fixed thread count) forked: yes (variable process count) Server compiled with.... -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D DYNAMIC_MODULE_LIMIT=256 -D HTTPD_ROOT="/opt/bw" -D SUEXEC_BIN="/opt/bw/bin/suexec" -D DEFAULT_PIDLOG="/var/bwlog/apache/logs/httpd.pid" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_ERRORLOG="logs/error_log" -D AP_TYPES_CONFIG_FILE="/etc/bw/apache/mime.types" -D SERVER_CONFIG_FILE="/etc/bw/apache/httpd.conf"
This is what it is referring to -- APR's default for the current platform. -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE (Please don't say you want it in an understandable format :) ) Did I miss your point?
I'd suggest we extend the documentation to say: look for APR_USE_.*?_SERIALIZE Anyway, those are *two* -- which is the default? The optimal thingy for this platform of mine?
>Anyway, those are *two* -- which is the default? One is the default for cross-process mutexes while the other is the default (and in fact only implementation) for intra-process mutexes. . I doubt that this geeky stuff from -V should really be pointed to by that particular doc...