should thread termination generate SIGCHLD in parent process?

• Next message: Tobias Ringström: "[PATCH] IDE block device trouble, mostly CD-related"
• Previous message: Rik van Riel: "2.2.15 fairsched"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I know linux uses one-to-one thread to process model, but I'm still
suprized to be getting a SIGCHLD back some time after the last thread has
exited without error and apparently having done it's job correctly. It is
always when I try to close /dev/dsp that one of the child processes (I
think the manager thread) goes zombie and the already <defunct> zombie
child threads die off that this signal gets generated and shows up in the
parent process. Is this the expected behavior? Why does the signal
always show up during the close(dsp_fd)?

I am running 2.2.14 and glibc 2.1.

Thanks in advance for any advice,

Britton Kerin

-
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/

• Next message: Tobias Ringström: "[PATCH] IDE block device trouble, mostly CD-related"
• Previous message: Rik van Riel: "2.2.15 fairsched"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:13 EST