topic Idle or process running in Operating System - HP-UX

Idle or process running

Suvadip De — Wed, 01 May 2002 14:15:35 GMT

I want to identify whether a terminal is sitting idle or a process is running on the terminal . (both shows idle times when using "w" command)
Please someone help its urgent!!!

Re: Idle or process running

Jeff Schussele — Wed, 01 May 2002 14:20:54 GMT

Hi Suvadip,

There will always be some processes running even when the system is "isle".

What you need to do is list the processes & search for the process in question. If you know the process_name then do

ps -ef | grep process_name

If you don't know the process name but do know the username then do

ps -ef | grep username

This will list all processes started by username.

HTH,
Jeff

Re: Idle or process running

Helen French — Wed, 01 May 2002 14:21:29 GMT

Hi Suvadip:

Try these commands:

# ps -aef | grep term_name
# whodo
# gpm

HTH,
Shiju

Re: Idle or process running

Jeffrey Davis_1 — Wed, 01 May 2002 14:24:59 GMT

Hi. I agree. Run the following:
ps -t tty?? (for tty in question to get user)
ps -eaf | grep (to get main PID)
ps -eaf | grep

(to get other processes spawned & time active)

Re: Idle or process running

harry d brown jr — Wed, 01 May 2002 14:25:30 GMT

If you want to log them off after some period of inactivity, providing they are sitting at a shell prompt, put this in the .profile:

readonly TMOUT=300

after 5 minutes of inactivity at a SHELL prompt ONLY, it will log them out!

If they are using anything, like vi, emacs, piping output to more, whatever, they will not be logged out.

live free or die
harry

Re: Idle or process running

Bill Hassell — Wed, 01 May 2002 15:19:15 GMT

Processes and terminal (tty connections) do not necessarily go together. An idle terminal may be a shell waiting for command from the user, which consumes no CPU time. The user may have started several background processes and then logged out which means that the processes are no longer associated with a terminal connection.

So the problem is more complicated than the simple w command can handle. Instead, you'll want to look at processes owned by each user, something like this:

UNIX95= ps -e -o time,ruser,args | sort -r | more

which sorts all the processes by amount of time accumulated. Or you could:

UNIX95= ps -e -o time,ruser,args | grep -v root | sort -r | more

to get rid of all the root processes. Or you could summarize by each user:

UNIX95= ps -e -o time,ruser,args | grep -v root | sort -r | more

Now, knowing which user is accumulating lots of time is not necessarily the best way to eliminate a performance issue unless there is a runaway program...but then it would pop to the top of the above lists.