Today in #httpd, someone asked why the CacheLock directive wasn't being recognised.
Turns out he was using httpd 2.2.3 and CacheLock was introduced in 2.2.15, however no documentation (even the change log at http://www.apache.org/dist/httpd/CHANGES_2.2) explicitly says which version a directive is introduced in; I had to make an educated guess based on the "thundering herd" description. Postfix does this; address_verify_relayhost (default: $relayhost) Overrides the relayhost parameter setting for address verification probes. This information can be overruled with the transport(5) table. This feature is available in Postfix 2.1 and later. Would it be particularly difficult to start doing this for httpd too? If not for 2.2.x, at least consider it for 2.4.x Regards, Mark. -- Mark Watts BSc RHCE MBCS Senior Systems Engineer, Managed Services Manpower www.QinetiQ.com QinetiQ - Delivering customer-focused solutions GPG Key: http://www.linux-corner.info/mwatts.gpg
signature.asc
Description: This is a digitally signed message part
