[Mono-list] RE: Releasing Named Mutexes
jeffc at sourcegear.com
Mon Feb 6 17:13:38 EST 2006
I sent word to the customer reporting this issue within Vault. They are
saying the named mutexes are still locked *days* after they send SIGINT
to a mono/Vault application on Mono 188.8.131.52 within RedHat Ent v3. The
sixty second behavior is not taking place.
What would be causing this behavior? Is there anyway to release a mutex
in this state?
mono-list-request at lists.ximian.com wrote:
> Message: 5
> Date: Mon, 06 Feb 2006 12:15:24 +0000
> From: Dick Porter <dick at ximian.com>
> Subject: Re: [Mono-list] Releasing Named Mutexes
> To: mono-list at lists.ximian.com
> <1139228125.32502.383.camel at hagbard.apathetic.discordia.org.uk>
> Content-Type: text/plain
> On Fri, 2006-02-03 at 09:09 -0600, jeff clausius wrote:
>> If a piece of code creates a named mutex is sent a SIGINT, short of a
>> restart, how can Mono release the named mutex?
>> Is there a Mono daemon or other process which controls named mutexes,
>> semaphores, pipes, etc.?
> I believe I answered this question on this list a couple of days ago:
> If you need more specific answers, please let me know which bits I can
> explain in more detail.
> - Dick
More information about the Mono-list