I am using centOS, sometimes the system just does not respond at all. In windows box, I can ctrl-alt-delete.
On a Linux machine, how should I handle this?
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.Sign up to join this community
If you have a keyboard attached, you could do the RESUIB method. Otherwise try to ssh into your box, and us top, ps and the usual helper and log checker programs to hunt down your problem.
There are the so-called "Magic SysRq keys" -- a set of keypresses that can be embedded at kernel level and will be honored as long as both the kernel process and the keyboard interrupt are still being listened to, and can be called by alt-SysRq-keypress.
These can perform various emergency tasks such as an emergency S ync of all mounted filesystems, k I lling all active tasks, or even forcing a hard re B oot.
However, linux in general needs to be pretty far gone for extreme measures like that to be the only remaining solution. Use only with extreme caution and when all else has failed.
As others have mentioned, though, "doesn't respond" is a bit vague. Can you clarify what is or isn't happening?
IMHO, There is no such ctrl+alt+del key-combination for Linux. But to check, why the machine get hangs, you can do either:
- Press alt+ctrl+f1, and observe the command "top", to see "who"/"which program" is eating up the cpu and causing the hang.
- You can place "system-monitor" in the taskbar, whose indicator will show the cpu-usage, for observation.
On linux systems processes can be observed by using commands such as
sudo ps waux to see a list with all users and full paths). Lots of programs such as
top can help you sort and monitor behaviors. You can then send the system commands to control those process using there process id. For example you can use
killall to terminate anything on the system.
Some system monitors like my favorite
htop will even allow you to attach traces to running processes to see exactly what they are up to and send them kill signals right from the observer.
There are some gui variants of these process monitors, but I have no experience with them. In Gnome you might look at
system-monitor. There is also something known as Linux Process Explorer.