Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4D6BE6B8.9040507@simonecaruso.com>
Date: Mon, 28 Feb 2011 19:17:28 +0100
From: Simone Caruso <info@simonecaruso.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: modules-dev@httpd.apache.org
Subject: Re: Help with apr mutex
References: <4D6BDAB9.9090907@simonecaruso.com>
 <AANLkTimZxvm209Uajp1F2TKiWLBMvqGN1Cq6RjbF9xpx@mail.gmail.com>
In-Reply-To: <AANLkTimZxvm209Uajp1F2TKiWLBMvqGN1Cq6RjbF9xpx@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 28/02/2011 18:53, thomas bonfort wrote:
> a few things to try:
>
> * you should use APR_STATUS_IS_EBUSY(s) instead of ... == APR_EBUSY
> * after creating the mutex, you might have to set permissions on it:
> #ifdef AP_NEED_SET_MUTEX_PERMS
>     rc = unixd_set_global_mutex_perms(mutex);
>     if(rc != APR_SUCCESS) {
>        ap_log_error(APLOG_MARK, APLOG_CRIT, rc, s, "Could not set
> permissions on global parent mutex %s", mutex_name);
>        return rc;
>     }
> #endif
>
> * I *think* that calling the lock functions twice from a same thread
> (without unlocking first) can have undefined behavior, i.e. don't do
> the lock() just after the trylock() call.
>
> regards,
> thomas

Thanks Thoms,
i'm going to try your code!

-- 
Simone Caruso
IT Consultant
+39 349 65 90 805
p.iva: 03045250838