kill actually passes certain signals to processes, and the default is to try
to shut it down gracefully (using SIGTERM i think)
the short of it, is you can try
kill -9 process_id
to forcefully bring it down.
well, the long of it, for a start is to read up on signals, and the obvious
places are
man kill
man 2 kill
man 7 signal
----- Original Message -----
From: "rikona" <[EMAIL PROTECTED]>
To: "Stephen Kuhn" <[EMAIL PROTECTED]>
Sent: Thursday, June 12, 2003 02:41
Subject: Re[5]: [newbie] Backdoor for crashes?
> Hello Stephen,
>
> Wednesday, June 11, 2003, 4:17:46 AM, you wrote:
>
> >> I tried 'kill 1452' to > get rid of X, and that wouldn't stop it
> >> either. A 'kill -9 1452' > apparently killed the machine. Reboot
> >> time.
>
> SK> Ain't it all the more easy to login via telnet or ssh from another
> SK> machine and just kill the offending process(es)? Or is that too easy?
>
> That's exactly what I did, but it didn't kill it. I'd run top, get the
> PID, exit top, kill it, go back to top, and it's still there. Any idea
> why?
>
> --
> Thank you,
> rikona mailto:[EMAIL PROTECTED]
>
>
>
----------------------------------------------------------------------------
----
> Want to buy your Pack or Services from MandrakeSoft?
> Go to http://www.mandrakestore.com
>
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
