On Wed, Mar 13, 2019 at 6:53 AM Yann Ylavic <ylavic....@gmail.com> wrote:
> On Wed, Mar 13, 2019 at 11:47 AM Yann Ylavic <ylavic....@gmail.com> wrote: > > > > On Fri, Mar 8, 2019 at 9:19 PM William A Rowe Jr <wr...@rowe-clan.net> > wrote: > > > > > > On Wed, Feb 27, 2019 at 5:06 PM William A Rowe Jr <wr...@rowe-clan.net> > wrote: > > >> > > >> Do we want to do something about de-prioritizing sysv semaphores > > >> on linux by default with the 1.7.0 release? > > > > > > Comments? I know some distributors already hack around our default > > > autoconf locking mechanism choice on modern Linux. > > > > I'm +1 on this one, proc-pthread should be the default on linux (and > > possibly solaris too if not already the case). > > Actually on all systems with both pthread_mutexattr_setpshared() and > pthread_mutexattr_setrobust[_np](). > ISTM that on some systems there is pthread_mutexattr_setrobust() w/o > the _np suffix (like *BSD), so we might want to check it for > HAVE_PTHREAD_MUTEX_ROBUST in apr_threads.m4 too.. > Is anyone prepared to move on this work for 1.7.0 in the very short term? I agree this is the right approach.
