Socket/SHM/Sem Ids and child processes

Socket/SHM/Sem Ids and child processes

Post by Mitch Gorm » Sun, 19 Jan 1992 02:19:42



        I have the following situation:  I am responsible for a particular
TLCSC of a software system, which will be composed of several (9, actually)
processes.  There will be one large SHM area, common to all CSCs, and I
intend to have a SHM area local to my own CSC.  There is one process which
controls the others within my CSC, and it is invoked by the highest-level CSC
in the system.

        Okay.  If the main process of my CSC shmgets the id of the global
area, and semgets a semaphore used within my CSC, and then forks/execs to create
the other processes within my CSC, is it safe for me to place those ids within
the local SHM area?  Are these ids the same regardless of which process does
a 'get with a particular key?

        Empirically, I've found this to be true, however I can vaguely recall
reading somewhere (I think it was something on the IBMLink network) to the
effect that this is a Bad Thing.  Anyone know for sure?

        Thanx.

        Mitch



 
 
 

1. Getting a child and child's child process-id

 Why not just have the parent fork twice ??? Saves a lot of trouble ...
--


#  Have you read your Book In Basic Life Education today ? You should !!  #
#  Any views I express are not necessarily those of Brighton Polytechnic  #
###################### "surivorter erutangis a ma I" ######################

2. Man bites dog.

3. Comparison expression

4. Process Id for the child process that is dying

5. FreeBSD 3.3

6. How to determine a process ID of a child process?

7. Installing two Network Cards in Debian 2.1 Distribution

8. System V shm/sem calls under Mach

9. SHM** and SEM** kernel parameters in Sol2.4 - HOW ?

10. POSIX shm, sem & aio

11. smail failed to reap child process: No child processes

12. how to kill a child process that runs other children processes