TIP: Click on subject to list as thread! ANSI
echo: cis.misc_info_soapbox
to: Zack Sessions 76407,1524 (X)
from: Mark Griffith 76070,41
date: 1990-09-01 06:27:07
subject: #6424-#dead procs

#: 6437 S14/misc/info/Soapbox
    01-Sep-90  06:27:07
Sb: #6424-#dead procs
Fm: Mark Griffith 76070,41
To: Zack Sessions 76407,1524 (X)

Zack,

Gshell keeps a path open to all child processes so it knows when they are still
active by checking the open path list.  This is how you get the "processes
still active" message when you try to stop Gshell with child processes still
running.

You could setup a sortof timed wait by having the child process send a signal
to the parent when it is just about ready to end.  The parent can then setup a
signal and using the signal() function, get interrupted when the child dies. 
The child would have to get the parent's pid from it' process descriptor.  The
parent, in turn, could keep a list of process id's that it forks so it knows
when all of them are dead.

Mark

There are 2 Replies.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.