Xref: utzoo comp.unix.xenix:1629 comp.unix.microport:165 comp.sys.att:2713
Path: utzoo!mnetor!uunet!husc6!cmcl2!phri!manhat!mancol!samperi
From: samperi@mancol.UUCP (Dominick Samperi)
Newsgroups: comp.unix.xenix,comp.unix.microport,comp.sys.att
Subject: IPC facilities (shared memory)
Message-ID: <335@mancol.UUCP>
Date: 7 Mar 88 22:02:07 GMT
Organization: Manhattan College, NYC, USA
Lines: 16
Keywords: IPC, shared memory, semaphores

I've used the System V IPC facilities (shared memory and semaphores) on
an AT&T 3B2, and on an AT-compatible running Microport's UNIX, but had
some difficulty porting the programs to SCO Xenix. In the Xenix environment
a parent process can create a shared memory segment, and attach it, but
a forked child process gets an "invalid argument" error when it tries to
attach the same segment. The child process does indeed use the same segment
identifier that the parent did.

Has anyone used the SCO Xenix IPC facilities? More generally, what kind
of applications have the IPC facilities (on any System V machine) been
used for? I haven't seen any applications programs that use them.
-- 
Dominick Samperi, Manhattan College, NYC
    manhat!samperi@NYU.EDU           ihnp4!rutgers!nyu.edu!manhat!samperi
    philabs!cmcl2!manhat!samperi     ihnp4!rutgers!hombre!samperi
              (^ that's an ell)      uunet!swlabs!mancol!samperi