Subject: Re: [Boost-bugs] [Boost C++ Libraries] #9321: named mutex permissions are not reset after application crash
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-10-30 20:50:13
#9321: named mutex permissions are not reset after application crash
-------------------------------------------------+-------------------------
Reporter: Marcus Ackermann | Owner: igaztanaga
<Marcus.Ackermann@â¦> | Status: new
Type: Bugs | Component:
Milestone: To Be Determined | interprocess
Version: Boost 1.50.0 | Severity: Problem
Resolution: | Keywords:
-------------------------------------------------+-------------------------
Comment (by igaztanaga):
The behavior is not a bug, as the mutex is still there until you
explicitly remove it (POSIX lifetime semantics). It's similar to files. A
process can create a file but the second process might not have
permissions to remove it. It might not be similar to Windows native
reference-counted resources (when the last process holding the resource
dies the resources is freed by the OS), but it's not a bug..
If you need to share the mutex between processes you should put the
appropriate permissions in the object (like the ones you need if you
create a file). You can use unrestricted permissions instead of standard
permissions if that doesn't cause security problems in your application.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/9321#comment:1> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:14 UTC