What is equivalent of CtrlAltDel in Unix?

[sbasak]

In Unix, the "ps -ef" command shows all running processes. This is probably equivalent of Ctrl+Alt+Del in Windows. But I like to know how one can determine whether a process is "Not Responding" ?

Can anyone help?

Thanks.

[mendhak]

What is equivalent of CtrlAltDel in Unix?

[sbasak]

I didn't understand what you meant!

[parksie]

Originally posted by sbasak
In Unix, the "ps -ef" command shows all running processes. This is probably equivalent of Ctrl+Alt+Del in Windows. But I like to know how one can determine whether a process is "Not Responding" ?

Can anyone help?

Thanks.

Well...if it's got 0% CPU usage, or top thinks it's a zombie, perhaps.

[esmerelda]

Stupid answer I regret posting: If you've got a super user account and are running solaris then type halt and when you get the ok prompt type boot, but otherwise, i'm not sure...

Good answer you'll listen to: Type "ps aux" and it should list everything... including cpu usage, which if it's 0%, then type "kill -9 " and the processes ID number (second column from the left I think...)

[esmerelda]

Originally posted by mendhak

I feel like that sometimes... Expecially when I'm compiling C code and it gives me 2 million errors (yes, this has actually happened, and all because of a rogue " in a header file...)

[mendhak]

2 million???

[parksie]

Normally the compiler gives up at about 200

[sbasak]

ps -ef produces following columns

UID PID PPID C STIME TTY TIME CMD

UID = user
PID = process id
PPID = process id of parent process
C = processor utilization for scheduling
STIME = start time
TTY = controling terminal
TIME = cumulative CPU time
CMD = command to create the process

Now can you please tell me what column value will indicate a "Not responding" process and how can I stop that particular process?

[parksie]

The reason Windows decides that something's not responding is when its message queue starts to fill up.

Under Unix, the architecture is different so there's almost no way to tell.

If your process isn't responding, then you'll notice because it ain't doing anything, or it's doing something different than it should be (i.e. infinite loop = 100% CPU usage, which is a dead giveaway for anything other than SETI).

[sbasak]

Thanks, just wondering what's message queue...?

And how do I get to know whether a "proces ain't doing anything"? Will it show 100 C value (CPU utilization) under ps -ef?

[parksie]

You'd have to know the internals of the Win32 API to know about the message system, but messages get passed around to all Windows programs.

Don't worry about it.

It depends on how the program's died. Basically, if it stops being useful to you, you *know* it's stopped responding!

[esmerelda]

Originally posted by mendhak
2 million???

400,000 lines of code that compiles into a dynamically compilable MUD engine. It's a ***** if you make a mistake, and the error which showed up was in a header file which is needed by all the files. *grumbles*

[esmerelda]

Originally posted by parksie
If your process isn't responding, then you'll notice because it ain't doing anything, or it's doing something different than it should be (i.e. infinite loop = 100% CPU usage, which is a dead giveaway for anything other than SETI).

I like seti, but it eats up your memory so much you wish that earth was the only planet in the universe...

[parksie]

[mike@relativity mike]$ ps aux | egrep '(seti|MEM)'
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
mike     23795 93.6  3.0 17972 15680 vc/1    RN   Oct29 1280:24 ./setiathome

...3% for me, which == 15MiB *shrug*

[esmerelda]

You ever run the windows version? Obviously not...

[Emo]

Originally posted by esmerelda
I like seti, but it eats up your memory so much you wish that earth was the only planet in the universe...

my SETI usually take about 15MB.... but I don't really like teh 100% CPU usage all the time

-Emo

[parksie]

It's on Idle, it won't run if anything else needs it.