Xref: utzoo comp.unix.questions:15315 comp.unix.wizards:17444 comp.sources.wanted:8301
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!apple!sun-barr!cs.utexas.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.sources.wanted,comp.unix.i386
Subject: Re: Shared Mem, Msg queues, Semaphores  Code fragments wanted
Keywords: IPC XENIX shared memory segments interprocess communication
Message-ID: <2313@auspex.auspex.com>
Date: 1 Aug 89 17:42:45 GMT
References: <100@norsat.UUCP> <30715@ism780c.isc.com>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Followup-To: comp.unix.questions
Organization: Auspex Systems, Santa Clara
Lines: 14

(This is generic UNIX stuff - generic, at least, to systems that have
picked up S5 IPC - so we move it here to "comp.unix.questions"....)

 >The "AT&T UNIX System V/386 Programmer's Guide" has a whole chapter on
 >IPCs.  This includes full listings of test programs that exercise all
 >aspects of the IPC system calls.  I haven't tried them, but they look
 >pretty good.  I think you'll find them a great help.
 >
 >Of course, XENIX is not UNIX...

Yes, but it's derived from UNIX, and I'd expect that whoever put S5 IPC
into it probably used as much of AT&T's code as possible.  The vendors
of XENIX System V may even claim SVID compliance for that part of the
system....