05-30-06 06:12 AM
Paul Martin <ironheadjones@verizon.net>:
> Under Windows XP you can hit 'ctrl-alt-del' to bring up the task
> manager to view running applications and processes and see which
> applications are not responding (so you can shut them down).
>
> What's the right way to do this under Debian Linux?
Run "top" or "ps" ("ps fax | less"). Note the process ID (PID) of the
process, then you can "kill -HUP $PID" where $PID == the number.
Simpler: "ps fax | grep $WHATEVER_YOU'RE_LOOKING_FOR", then "kill -HUP
$PID".
If it's still there after -HUP, try kill -9.
Your user login ID won't be able to kill root owned processes, only
your own. Instead, you'll have to login as root to affect them. Be
careful with this. You can always "/etc/init.d/$BLAH start" them
again, but never *expect* things to die gracefully. Hope, yes.
Expect, no.
Eg., what happens when you shoot mysqld in the head[*]? I'd expect
corrupted tables. Perhaps mysqld can repair them when it restarts,
but do you want to bet on that, with your valuable data?
[*] I've actually worked for large corps that do this regularly.
Instead of gracefully shutting down the db, they just shoot it in the
head and rely on recovery routines to fix whatever corruption that
caused. Why? I've no idea. Perhaps it's related to watching Windows
crash regularly, and it seems able to drag itself back to life, so why
not a db?
--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://www.spots.ab.ca/~keeling Linux Counter #80292
- - Spammers! http://www.spots.ab.ca/~keeling/emails.html
http://www.ietf.org/rfc/rfc1855.txt
[ Post a follow-up to this message ]
|