Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!Think.COM!barmar
From: barmar@Think.COM
Newsgroups: comp.unix.ultrix
Subject: Re: Firing up a process and not wait()ing on it..
Message-ID: <32382@news.Think.COM>
Date: 21 Dec 89 02:32:18 GMT
References: <1989Dec19.191032.21857@lavaca.uh.edu> <2308@bacchus.dec.com>
Sender: news@Think.COM
Distribution: na
Organization: Thinking Machines Corporation, Cambridge MA
Lines: 17

In article <2308@bacchus.dec.com> klee@decwrl.dec.com writes:
>In article <1989Dec19.191032.21857@lavaca.uh.edu>, jet@lavaca.uh.edu (J.
>Eric Townsend) writes:
>> While in process foo, I want to crank up process bar
>> and have it run independently of foo. 
>The standard way of doing this is to fork (or vfork) and execl (or
>execv).

Don't you still have to wait() for it to prevent the child process from
becoming a zombie when it exits?

I think some versions of Unix check whether the parent has set up a handler
for the SIGCHILD signal when deciding whether to zombify the child.
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar