Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!sgi!shinobu!odin!moose.asd.sgi.com!jwag
From: jwag@moose.asd.sgi.com (Chris Wagner)
Newsgroups: comp.sys.sgi
Subject: Re: Help Requested on Arenas
Message-ID: <10162@odin.corp.sgi.com>
Date: 10 Jul 90 16:33:30 GMT
References: <1990Jul10.060216.1504@cs.UAlberta.CA> <9007051819.AA09079@trouble.cs.nps.navy.mil>
Sender: news@odin.corp.sgi.com
Reply-To: jwag@moose.asd.sgi.com (Chris Wagner)
Organization: Silicon Graphics, Research & Development
Lines: 10

Yes, in fact in 3.2 one has to come up with ones own solution - opening
a pipe or file
seems the easiest.
In 3.3 we have added the usputinfo and usgetinfo functions that give you
a single
pointer, thus the originating process can use usputinfo to store a
pointer to a data structure
that further defines what addresses in the arena are being used for what

Chris Wagner