Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!POSEUR.JPL.NASA.GOV!earle
From: earle@POSEUR.JPL.NASA.GOV (Greg Earle - Sun JPL on-site Software Support)
Newsgroups: comp.windows.x
Subject: Re: xperfmon under SunOS 4.0.X
Message-ID: <8911230421.AA02003@poseur.jpl.nasa.gov>
Date: 23 Nov 89 04:21:31 GMT
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 21

>However, the patch in xperfmon.sun4_0.patch in contrib on expo worked just
>fine for us (SunOS 4.0.1/3, Sun-4 and SPARCstations).

On a totally unrelated note, I have found that `xperfmon' (with the
aforementioned patch installed) becomes The Program That Wouldn't Die.
If I SIGHUP it, or use `xkill' on it, or hit my `Exit' gadget in my awm
titlebar on top of it (f.exit function), etc., the window is unmapped;
but the `xperfmon' process itself doesn't exit - it still sits there, and
starts to chew up CPU while apparently stuck in the deadly embrace of
an ioctl()/select() loop.  I have to SIGTERM the bugger to make it go away.

Has anyone else noticed this?

[ Particulars: Sun-3/260C, SunOS 4.0.3+; all 10 patches applied,    ]
[ Purdue 2.0 + 2.1, gcc 1.34 compiled; `xperfmon' gcc 1.36 compiled ]

--
	Greg Earle
	Sun Microsystems, Inc. - JPL on-site Software Support
	earle@poseur.JPL.NASA.GOV	(direct)
	earle@Sun.COM			(indirect)