On Tue, Jul 03, 2001 at 02:46:39PM -0400, Jeff Trawick wrote: > Note that APR currently doesn't have the right information now to set > APR_PROCESS_LOCK_MECH_IS_GLOBAL properly, so we end up getting two > locks instead of one on some platform/mechanisms where it isn't really > needed. > > But assuming that we get more hints or whatever to turn on > APR_PROCESS_LOCK_MECH_IS_GLOBAL in more cases then magic should > happen.
How would we even go about determining this? Do we add this into apr_hints.m4 for each platform/OS that we know APR_PROCCESS_LOCK_MECH_IS_GLOBAL can be safely set, or can we somehow write an autoconf test for this? (I have no clue how we could write a test for this - this seems awfully complex). -- justin
