[ace-users] Files created for USYNC_PROCESS mutexes
Douglas C. Schmidt
schmidt at dre.vanderbilt.edu
Mon Sep 10 19:40:43 CDT 2007
> Windows does not show this. We have only been running this on Linux
> (RedHat) ES/AS 3.0+ and Solaris 9+ (Sparc), and do see it on those
> platforms, and as far as I know, they behave identically.
Ok, that's helpful info.
>> My guess is that you're simply seeing a consequence of the way in
>> which process-level locks are implemented on some platforms, but it
>> would be helpful if you could provide more info.
>I'll provide whatever information you think might be helpful.
> For what it's worth, in case it wasn't clear, it is not our
> intention to have the mutex remain locked if there are no longer any
> processes running. When the last process using the mutex is running,
> we'd like the mutex to unlock or even disappear entirely. The
> problem is that it remains locked, apparently due to the existence
> of the file.
. Use ACE_Process_Mutex not ACE_Mutex (... USYNC_PROCESS) since the
latter is really not intended for general use.
. That's not how the ACE_Process_Mutex stuff is designed to work. You
need to call remove() when you want it to go away.
Dr. Douglas C. Schmidt Professor and Associate Chair
Electrical Engineering and Computer Science TEL: (615) 343-8197
Vanderbilt University WEB: www.dre.vanderbilt.edu/~schmidt
Nashville, TN 37203 NET: d.schmidt at vanderbilt.edu
More information about the Ace-users