On Wednesday, April 3, 2013, Philip Martin wrote:
> Ben Reser > writes:
>
> > On Wed, Apr 3, 2013 at 12:29 PM, Jeff Trawick
> > >
> wrote:
> >> I'm not aware of any apr_file_lock() use within httpd, so you wouldn't
> >> regress anything (unless you're using third-party modules that use
> >> apr_f
Ben Reser writes:
> On Wed, Apr 3, 2013 at 12:29 PM, Jeff Trawick wrote:
>> I'm not aware of any apr_file_lock() use within httpd, so you wouldn't
>> regress anything (unless you're using third-party modules that use
>> apr_file_lock). But I guess you've introduced a third-party module that
>>
On Wed, Apr 3, 2013 at 12:29 PM, Jeff Trawick wrote:
> I'm not aware of any apr_file_lock() use within httpd, so you wouldn't
> regress anything (unless you're using third-party modules that use
> apr_file_lock). But I guess you've introduced a third-party module that
> uses apr_file_lock() or yo
Thanks for getting back to me Jeff, appreciate it!
It's SLES11, SP2 I believe. I suppose I'd have to consider any other modules
that I've included in my configuration as well any their usage of
apr_file_lock. It does seem like though, if I'm using "worker", and NFS isn't
in the mix, I'd want fl
On Wed, Apr 3, 2013 at 3:03 PM, Greg Lazar wrote:
> **
> The apr_file_lock routine, in the version of apr runtime library that I've
> currently built uses fnctl which does not appear to be thread safe. I need
> to use the worker MPM, so is it recommended that I build the apr runtime
> library to
The apr_file_lock routine, in the version of apr runtime library that I've
currently built uses fnctl which does not appear to be thread safe. I need to
use the worker MPM, so is it recommended that I build the apr runtime library
to use flock instead. NFS file systems aren't a concern in this c
