[Mono-bugs] [Bug 74680][Nor] Changed - Creating mutex on new I/O
layer returns wrong status
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Tue Sep 13 16:02:57 EDT 2005
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by mlasky at novell.com.
http://bugzilla.ximian.com/show_bug.cgi?id=74680
--- shadow/74680 2005-09-13 15:57:05.000000000 -0400
+++ shadow/74680.tmp.15245 2005-09-13 16:02:57.000000000 -0400
@@ -99,6 +99,13 @@
Named mutexes work fine as far as I know, the only issue is that they
dont automatically destroy themselves yet. But surely any app that
uses them for synchronisation has to be able to cope with another
instance having already created the mutex?
Fixing this is in progress; it has been bumped by other tasks though.
+
+------- Additional Comments From mlasky at novell.com 2005-09-13 16:02 -------
+I agree with your comments. Sometimes an application needs to know
+if it is the creator of the mutex or not. This is useful for knowing
+which instance of an application was running first.
+
+I will try and wait patiently for the fix.:o))
More information about the mono-bugs
mailing list