Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!versatc!icldata!altos86!dtynan
From: weber_w@apollo.com (Walt Weber)
Newsgroups: comp.unix
Subject: Re: System V IPC has no REMOVE_ON_EXIT bit
Message-ID: <1211@altos86.UUCP>
Date: 12 Jun 89 07:26:43 GMT
References: <1151@altos86.UUCP>
Sender: dtynan@Altos.COM
Reply-To: uunet!apollo.com!weber_w (Walt Weber)
Organization: Apollo Computer, Chelmsford, MA
Lines: 25
Approved: dtynan@zorba.Tynan.COM


In article <1151@altos86.UUCP> clp@altos86.Altos.COM (Chuck L. Peterson) writes:
>
>Am I missing something incredibly obvious, or does System V
>IPC lack a bit which indicates that the shared memory, semaphore, or
>message should be removed automatically when my process exits?

This behavior would seem to fly in the face of the understanding that the SYSV
IPC's are system-wide resources, and not "exported from a process".  The model
which appears to be most widely used (beware: limited sample!) is that a process
will be run from inittab which will create ("seed") the IPC feature with the
appropriate permissions, values, and sizes, and then exit.  All others will
block (or exit) if the environment they find is non-existent (or incorrect).

Why keep "placeholder" processes hanging around in the process table?

..walt...

>clp@altos.com


-- 
Walt Weber                            Apollo Computer          
(508) 256-6600 x8315                  People's Republic of Massachusetts
-The views expressed herein are personal, and not binding on Apollo-