Xref: utzoo comp.unix.xenix:1647 comp.unix.microport:185 comp.sys.att:2723
Path: utzoo!mnetor!uunet!husc6!bbn!mit-eddie!uw-beaver!cornell!batcomputer!itsgw!steinmetz!davidsen
From: davidsen@steinmetz.steinmetz.UUCP (William E. Davidsen Jr)
Newsgroups: comp.unix.xenix,comp.unix.microport,comp.sys.att
Subject: Re: IPC facilities (shared memory)
Message-ID: <9844@steinmetz.steinmetz.UUCP>
Date: 8 Mar 88 15:21:40 GMT
References: <335@mancol.UUCP>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 17
Keywords: IPC, shared memory, semaphores


  SysV shared memory segments are inherited by the child, like any other
open handle. If you open the segment and then do a fork, the child has
access. If you fork and then open, the child will have to open, too.

  I have used the shm stuff without too much trouble, but the semiphores
really have me going. I can make them work as traditional semiphores,
notify and wait model, but when I start using the counts, I get some
funny results.

  I'm still working on this, and will try it in a number of systems to
be sure the bug isn't in Xenix.

-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me