Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!agate!dog.ee.lbl.gov!horse.ee.lbl.gov!torek
From: torek@horse.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.internals
Subject: Re: IPC keys
Keywords: SYSV IPC
Message-ID: <13832@dog.ee.lbl.gov>
Date: 3 Jun 91 02:35:21 GMT
References: <1991Jun2.234335.12694@cs.umn.edu>
Reply-To: torek@horse.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 20
X-Local-Date: Sun, 2 Jun 91 19:35:21 PDT

In article <1991Jun2.234335.12694@cs.umn.edu> wsmith@cs.umn.edu
(Warren Smith [Randy]) writes:
>... Is there some sort of standard key management system that I'm
>unaware of?

There is a hack based on device and inode numbers, but it is just a
hack.

>If not, why was IPC implemented without addressing this problem?

The IPC that wound up in System V was never intended as a general
facility.  It exists because a special-purpose application running
on a special-purpose kernel had to move to a generic kernel, so they
stuck in a special-purpose IPC.  Unforunately, `they' were USDL,
the group in charge of System III.

Now you know. :-)
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov