* Aaron Solochek said: > kernel 2.2.13, sparcstation 5 (170mhz, 128mb), gcc 2.95.2. is the kernel compiled with that compiler? Can you tell that the processes that go defunct are ones that fork during their life span? If so, then that could be a problem with the kernel. After a parent forks, the kernel will try to notify the parent about the fact that a life of its child(ren) has ended by sending a signal. If this signal isn't received by the parent (e.g. by using waitpid or wait4) the child process will go zombie (<defunct>). If the application is coded properly and it still happens, it might mean that the kernel fails to deliver the SIGCHLD signal to the parent for some reason. It might be caused by the kernel compiled with 2.95.x gcc. Generally, it's safer to use gcc 2.7.2.3 to compile your kernels. marek
Attachment:
pgpIRcvPquaMa.pgp
Description: PGP signature