[svlug] Xlock gone awry
steve_williams at radixtek.com
Fri Sep 4 09:42:32 PDT 1998
I've just had a strange one and wondered if any of you with more
experience could shed some light. Last night, I left my machine
running Xlock (by picking "Lock Screen/Screen Saver" from the FVWM2
pop-up menu). Xlock was in `random' mode. When I got in this morning,
the screen was frozen, and I couldn't do anything to unfreeze it (but
I forgot to try switching to a virtual console).
I logged in remotely from another machine, and the load average on my
machine was up around 1.0, although top showed only 2 runnable
processes (top itself and xlock). xlock didn't seem to be
accumulating any run time however.
I tried, unsuccessfully, to kill xlock (via kill -9). I then killed
the X server and all of my X clients died (un)natural deaths. BUT
XLOCK KEPT RUNNING! No amount of "kill -9" would make it go away, and
the loadavg stayed up around 1.0. I have rebooted the machine in
order to go on with work today, but I was hoping to get more than 10
days of uptime.
Has anybody ever seen this behavior before? Does anybody know of a
work-around? Is there any further debugging information I should try
to collect if it happens again? I'm running a pretty vanilla RH5.1
setup on an Intel PD440FX motherboard. My graphics card is a Diamond
Stealth64 series 3000, and I am running the standard XFree86 X server.
I have applied all of the RedHat patches up through about July 14.
rpm -qa | grep "^X"
rpm -qa | grep xlock
Thanks in advance...
Steve Williams Radix Technologies, Inc.
Sr DSP Software Engineer 650.988.4754
Once you have flown, you will walk the earth with your eyes turned
skyward, for there you have been, there you long to return.
-- Leonardo da Vinci
echo "unsubscribe svlug" | mail majordomo at svlug.org
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ to unsubscribe
More information about the svlug