[no subject]

It appears that it is atomic as the man page for semget states:

        The  presence  in  semflg  of  the  fields  IPC_CREAT  and
        IPC_EXCL  plays  the  same role, with respect to the exis?
        tence of the semaphore set, as the presence of O_CREAT and
        O_EXCL  in  the  mode argument of the open(2) system call:
        i.e. the semget function  fails  if  semflg  asserts  both
        IPC_CREAT  and IPC_EXCL and a semaphore set already exists
        for key.

Don't know how I missed that.

-- 
Until later, Geoffrey                     Registered Linux User #108567
Building secure systems in spite of Microsoft


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00557" href="msg00557.html">[ale] perl new IPC::Semaphore and/or C semget()</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00557.html">[ale] perl new IPC::Semaphore and/or C semget()</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00559.html">[ale] get a free Linux Technical Resource Kit from Novell</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00557.html">[ale] perl new IPC::Semaphore and/or C semget()</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00541.html">[ale] Wireless</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00558"><strong>Date</strong></a></li>
<li><a href="threads.html#00558"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>