The pid's are kept in /var/run/
You may have already tried these, but I'll give them anyway:
#kill `cat /var/run/loopd`
or
#kill -s 9 `cat /var/run/loopd`
Type #kill -l
to see a list of signal names.
-Channon
-----Original Message-----
From: H M Kunzmann [mailto:herbert@dreamstroke.com]
Sent: Wednesday, February 26, 2003 2:13 AM
To: psyche-list@redhat.com
Subject: process cannot be killed
I have a process loopd that I just can't seem to
kill with any command I've used. I've sent it every
imaginable form of kill signal so far and it simply
does not respond.
vmstat gives this output:
procs memory swap io
system cpu
r b w swpd free buff cache si so bi bo in cs us
sy id
0 0 1 224 2856 16836 303504 1 0 1 0 0 0
0 1 0
showing that the process is swapped out.
I tracked down messages in /var/log/messages, since recent upgrades
I've been receiving the modprobe errors - cannot locate net-pf-10.
I added a line in the /etc/modprobe.conf to alias net-pf-10 to 'off'
(death to ipv6), and since then I've received no more errors, but
the process still hovers about consuming 70-95% CPU utilization.
I''ve searched the net and found similar problems and all they've
offered as solutions is to reboot.
This is a critical server and while slow, it still serves its purpose,
I could (shoudl) reboot it only during the weekend.
Is there no other way ??
--
Herbert Michael Kunzmann
Binary Chaos Magician
--
Psyche-list mailing list
Psyche-list@redhat.com
https://listman.redhat.com/mailman/listinfo/psyche-list
