Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!alberta!cdshaw
From: cdshaw@cs.UAlberta.CA (Chris Shaw)
Newsgroups: comp.sys.sgi
Subject: Re: Help Requested on Arenas
Message-ID: <1990Jul10.060216.1504@cs.UAlberta.CA>
Date: 10 Jul 90 06:02:16 GMT
References: <9007051819.AA09079@trouble.cs.nps.navy.mil>
Sender: news@cs.UAlberta.CA (News Administrator)
Organization: University of Alberta, Edmonton, Canada
Lines: 21

In article X zyda@trouble.cs.nps.navy.mil (michael zyda) writes:
>     In order for the other processes to have access to that allocated
>shared memory, the other processes must somehow obtain a pointer
>to that allocated memory. How is this done safely, i.e. what
>system routine do I call in process 1 to find a pointer to
>the first byte allocated by usmalloc in process 2?

Perhaps you could try opening a socket connection such that process 1 sets
up a service and the other process(es) open a simple client connection to 
process 1's service. Do some communication, figure who usmalloc'd what,
then close the connection and await a new one. This will serialize multiple
client starts into the common area. The rest of the communication could be
done via the shared memory.
Should work.

>     Michael Zyda
>     zyda@trouble.cs.nps.navy.mil
--
Chris Shaw     University of Alberta
cdshaw@cs.UAlberta.ca           Now with new, minty Internet flavour!
CatchPhrase: Bogus as HELL !