httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Ames <>
Subject Re: 2.0.34 - apr_lock_create fails on daedalus
Date Mon, 01 Apr 2002 17:41:41 GMT
Jeff Trawick wrote:

> 1) see what syscall failed and how to make it stop failing (OS tuning
>    perhaps?)

daedulus's truss doesn't have an option to follow fork()s :(  But I think I'll
switch to Plan B anyway...see below.

> 2) validate that SysV sem is the proper mutex mechanism we should be
>    using by default on FreeBSD

Probably not.  apache-1.3's ap_config.h defines HAVE_FLOCK_SERIALIZED_ACCEPT for
FreeBSD, but apr_hint.m4 doesn't have similar logic in 2.0.  I'll patch that,
and give it a shot.


View raw message