On Thu, Nov 19, 2009 at 11:09 AM, Joe Orton <[email protected]> wrote: > On Thu, Nov 19, 2009 at 06:47:56AM -0500, Jeff Trawick wrote: >> I envisioned the conf (perhaps a vendor conf) declaring something like >> >> MutexDir logs >> or >> MutexDir /var/apache2/2.2/locks >> >> The admin can then adjust the mutex methods as necessary and not worry >> about paths to locks. Or change MutexDir as necessary and not affect >> the mutex methods at all. MutexDir can be used as a preventative >> measure even if no file-based mutexes are currently configured. >> >> With the single directive solution, I don't see a way to declare "if >> lock files must be used, put them here." > > I guess that makes sense. I didn't see any need to configure that > separately; i.e. in a vendor build having the locks dir default to > DEFAULT_REL_RUNTIMEDIR would be sufficient. Joe
Right, the vendor config isn't a good example of when any Mutex configuration is needed, as they hopefully have set the default mutex type and locks dir default appropriate for almost all users. I'll try to get some working code, and meanwhile maybe somebody else will speak up.
