corey@cbnewsm.att.com (william.c.brown) (06/05/91)
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???? Thanks in advance. --Corey Brown AT&T NSD Alpharetta, GA 30202 (404)750-8071 att!alphlz!wcb
mahesh@sol.cs.fau.edu (Mahesh Neelakanta) (06/10/91)
> 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