Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Need Information about processes Post 802 by PxT on Friday 19th of January 2001 04:32:54 PM
Old 01-19-2001
You can use the 'ps' command to see which terminal a process is running on. You can then use 'finger' or 'w' or 'who' to see who is logged in on that terminal.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

processes

How can i kill the zombie processes,like using some background process which can help me reduce the process load on the server. the OS is AIX. (3 Replies)
Discussion started by: rajusom
3 Replies

2. UNIX for Dummies Questions & Answers

co-processes

Is it possible to have a main script (i will call it main.ksh) that executes say, 4 other scripts (sub_prog_1.ksh, sub_prog_2.ksh etc..) from within this main.ksh (simultaneously/in parallel), have them run in the background and communicate back to main.ksh when complete? My guess is to use... (1 Reply)
Discussion started by: google
1 Replies

3. UNIX for Dummies Questions & Answers

processes

What command string will locate ONLY the PID of a process and ouput only the number of PID of the process? (1 Reply)
Discussion started by: mma_buc_98
1 Replies

4. Shell Programming and Scripting

I need some example of Co-Processes

I want to know how to work the Co-Processes in kornshell scripts. So, I very need some script about Co-Processes! thanks ...:) (3 Replies)
Discussion started by: javalee
3 Replies

5. Shell Programming and Scripting

processes

does anyone know how to lower the sheduling priority of a process. (3 Replies)
Discussion started by: master_6ez
3 Replies

6. Filesystems, Disks and Memory

processes

write a program create two processes to run a for loop which adds numbers 1 to n , say one process adds odd numbers and other adds even numbers (1 Reply)
Discussion started by: jayaram_miryabb
1 Replies

7. UNIX for Dummies Questions & Answers

Processes

Can someone tell how to find out how long a process has been running? I want to find something that is usually there that the paging system can check on. Thanks (4 Replies)
Discussion started by: Beetlejuice
4 Replies

8. UNIX for Advanced & Expert Users

Monitoring Processes - Killing hung processes

Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go? Thank you Richard (4 Replies)
Discussion started by: ukndoit
4 Replies

9. Solaris

Identifying and grouping OS processes and APP processes

Hi Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages. Any free tools or scripts to do this? Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies

10. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
rwho(1) 						      General Commands Manual							   rwho(1)

NAME
rwho - show who is logged in on local machines SYNOPSIS
DESCRIPTION
produces output similar to the output of the HP-UX command for all machines on the local network that are running the daemon (see who(1) and rwhod(1M)). If has not received a report from a machine for 11 minutes, assumes the machine is down and does not report users last known to be logged into that machine. output line has fields for the name of the user, the name of the machine, the user's terminal line, the time the user logged in, and the amount of time the user has been idle. Idle time is shown as: If a user has not typed to the system for a minute or more, reports this as idle time. If a user has not typed to the system for an hour or more, the user is omitted from output unless the flag is given. An example output line from would look similar to: This output line could be interpreted as is logged into and his terminal line is has been logged on since September 12 at 13:28 (1:28 p.m.). has not typed anything into for 11 minutes. WARNINGS
output becomes unwieldy when the number of users for each machine on the local network running becomes large. One line of output occurs for each user on each machine on the local network that is running AUTHOR
was developed by the University of California, Berkeley. FILES
Information about other machines. SEE ALSO
ruptime(1), rusers(1), rwhod(1M). rwho(1)
All times are GMT -4. The time now is 02:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy