Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!rex!uflorida!shark!shark!mahesh
From: mahesh@sol.cs.fau.edu (Mahesh Neelakanta)
Newsgroups: comp.windows.open-look
Subject: Re: OLVWM leaving defunct processes
Message-ID: <MAHESH.91Jun9174646@sol.cs.fau.edu>
Date: 9 Jun 91 21:46:46 GMT
References: <1991Jun4.211114.19751@cbnewsm.att.com>
Sender: news@cs.fau.edu (NetNews)
Distribution: usa
Organization: Florida Atlantic University, Boca Raton
Lines: 19
In-Reply-To: corey@cbnewsm.att.com's message of 4 Jun 91 21:11:14 GMT
Nntp-Posting-Host: sol.cs.fau.edu


> I am currently running OLVWM 1.2 dated 3/30/91 on an
> SPARC-2 with 4.1.1.. My problem is that OLVWM seems to
> leave defunct process slots hanging around all over the
> place. I noticed this today after I was searching for
> a PID and saw all those defuncts.. Seems I get one 
> everytime I close an XTERM session...

> Has anyone else seen this problem??? Whats the fix, if any????


  I had similar problems with olwm in a SysV environment (386ix and hpux).
A temporary solution (which doesn't seem to affect anything else) is to
do a "signal(SIGCHLD, SIG_IGN)" instead of calling that reap_children
function. <defunct> processes (as I understand it) are zombies that don't
have a parent who is wait(2)'ing for them. If someone has a real solution
to this, please post it as I am sure that my solution is not the best one.

mahesh