Re: Hard kill a process?
- From: x0054 <x0054@xxxxxxxxx>
- Date: 02 Jun 2006 01:04:22 GMT
x0054 <x0054@xxxxxxxxx> wrote in
news:Xns97D2EEAEA1F1Cx0054indexcom@xxxxxxxxxxxxxx:
"Michael B. Trausch" <michael.trausch.no.spam@xxxxxxxxxxx> wrote in
news:atadnW_B0MRtfebZRVn-sQ@xxxxxxxxxxx:
x0054 wrote in <Xns97D2B9B6AC056x0054indexcom@xxxxxxxxxxx> on Mon,
May 29 2006 21:13:
I got a process that will not die :(. I tried "kill -9" and it still
does not die. It's a loop back process from a failed mount iso
command. But just in general what would be a way to kill a process
that hanged and does not respond ?
- Bogdan
It may be in a state of uninterruptable sleep. This is often the
case for a process waiting on I/O from a block device (such as mount)
where it may hang indefinitely. In this situation, the only way to
get rid of it is to wait for it to finally die off itself (which may
or may not happen), or to restart the system.
You may want to try to find out why that happened. The only times
that I have actually personally witnessed such types of things are
when I'm working with something connected that is hot-pluggable --
such as a USB device or something similar -- and the connection goes
awry (I had a hub that bit the dust, and the connections to the
devices on the hub were somewhat intermittent).
- Mike
What happen is I was trying to mount an iso CD image. The image was
corrupted however. I use '-o loop' to mount it, the mount failed
because the iso was corrupted but the loop device did not die by it's
self, like you mentioned, it was waiting for the I/O I guess. In the
end I had to restart.
This is a really ignorant question, I know little about the way kernel
does stuff, but, shouldn't there be a way to trekdown the memory used
by a process and just reclaim it? Even if the process is completely
stalled? I read that the kill command sends a signal to the process
which tells it to die. What I am wondering is, wouldn't it make it
easy then to write a program that purposely simulates the kind of
behavior I experienced to force it to remain in the memory. For
instance if some one wrote a virus like that.
Just wondering, if you can point me to an article that discusses this
topic more I would be grateful. It sounds very interesting to me.
- Bogdan
This is in relation to my prior question. Often times I need to mount
..iso files on my server. It's not a problem if the .iso file is all
good, but once in a while it is corrupted, as in the case above. If the
file is corrupted the 'loop' process hangs. My question is, is there a
way to prevent that.
I use:
mount something.iso /mnt/tmp -o loop
should I add anything to that command to prevent loop from hanging
incase the .iso is corrupted?
Thank you,
- Bogdan
.
- Prev by Date: Re: Install boot loader on second drive.
- Next by Date: Re: What going on with the Puppy linux forums?
- Previous by thread: Re: Teen Sister In the shower hidden Cam
- Next by thread: Re: What going on with the Puppy linux forums?
- Index(es):
Relevant Pages
|
