[4223] in SIPB bug reports
xsrceensaver on Solaris
daemon@ATHENA.MIT.EDU (jweiss@MIT.EDU)
Wed Nov 3 16:00:16 1993
From: jweiss@MIT.EDU
To: bug-sipb@MIT.EDU
Cc: jweiss@MIT.EDU
Date: Wed, 03 Nov 93 11:34:04 EST
I noticed, after being logged in for a few days that I was
accumulating a growing list of <defunct> processes. Upon
investigating 26 of my 27 defunct processes had the same ppid.
Coincidentally, (or not) this was the pid of my xscreensaver. In fact
when I exited xscreensaver these 26 processes finished dying.
I then started a new xscreensaver and attempted to create more defunct
processes. I locked and unlocked my screen; no new defunct processes.
I did it again; 1 new defunct process. And again; another new defunct
process. This sounds suspiciously like a signal handeler is not being
re-registered (welcome to sysV signals), although I haven't looked at
the code or anything.
Here are my relevant xresources, for reference:
xscreensaver*iconPixmap: /afs/sipb.mit.edu/project/sipb/bitmaps.x11/SigmaPiBeta
xscreensaver*icon.bitmap: /afs/sipb.mit.edu/project/sipb/bitmaps.x11/SigmaPiBeta
xscreensaver*float.bitmap: /afs/sipb.mit.edu/project/sipb/bitmaps.x11/yinyang
XScreensaver*autoLock: true
XScreensaver*reverseVideo: true
XScreensaver*encryptedKey: bzA1m9goekSJE
XScreensaver*geometry: +0-0
XScreensaver*lockCommand: zaway /tmp/away_${USER}
Jonathon
