Messages in this thread | | | From | allbery@kf8nh ... | Date | Tue, 20 Jul 1999 20:31:46 -0400 (EDT) | Subject | Re: Patch: CLONE_PPID (was kernel thread support - LWP's) |
| |
On 20 Jul, Alan Curry wrote: +----- | Jeremy Fitzhardinge writes the following: | >On 20-Jul-99 Matthew Kirkwood wrote: | >> There may be code out there which gets confused on receiving a SIGCLD | >> for (or wait()ing on) a child which it doesn't remember creating. | > | >Any process can have children it doesn't know about creating, so this is not a | >new situation. It doesn't seem worth adding cruft to prevent. | | Are you prepared to give an example? +--->8
Any process that fork()s without wait()ing, then in the parent exec()s something else. The new image won't have any clue about the forked child.
-- brandon s. allbery os/2,linux,solaris,perl allbery@kf8nh.apk.net system administrator kthkrb,heimdal,gnome,rt allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering kf8nh We are Linux. Resistance is an indication that you missed the point.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |