Actually I created a dedicated thread [1] for this issue, since it was
quite out of topic here.
Moreover I was about to update that thread with a new patch (taking
into account the latest changes on proc_mutex, ie.
APR_LOCK_DEFAULT_TIMED introduced with
apr_{proc,thread}_mutex_timedlock).
So I con
Is there any chance this could be integrated into 1.6, or any fix that
allows apr_os_proc_mutex_put/get() on posix semaphores (sem_t)?
Regards,
Yann.
On Tue, Apr 15, 2014 at 12:37 AM, Yann Ylavic wrote:
> Also, it seems that the posix sems (ie. sem_t from semaphore.h) are
> handled as a file des
On Mon, Apr 14, 2014 at 10:19 PM, Jeff Trawick wrote:
> dev@apr has an aggravating reply-to setting :( Please try again to the
> list...
>
Serious CTKI bug, still inverstigating :)
On Sun, Apr 13, 2014 at 8:17 PM, Jeff Trawick wrote:
>
> trunk r1587063
> 1.5.x r1587064
Thanks for applying thi
On Thu, Mar 27, 2014 at 8:15 AM, Yann Ylavic wrote:
> Hi,
>
> when using the following code :
>
> pthread_mutex_t *mymutex;
> apr_proc_mutex_t *apmutex = NULL;
> apr_os_proc_mutex_t osmutex = {0};
> apr_proc_mutex_create(&apmutex, NULL, APR_LOCK_PROC_PTHREAD, p);
> apr_os_proc
Hi,
when using the following code :
pthread_mutex_t *mymutex;
apr_proc_mutex_t *apmutex = NULL;
apr_os_proc_mutex_t osmutex = {0};
apr_proc_mutex_create(&apmutex, NULL, APR_LOCK_PROC_PTHREAD, p);
apr_os_proc_mutex_get(&osmutex, apmutex);
mymutex = osmutex.pthread_interproc
