Sponsored Content
Top Forums Shell Programming and Scripting how to know the running processes. Post 302503377 by methyl on Thursday 10th of March 2011 10:37:22 AM
Old 03-10-2011
See "man ps" for whatever Operating System you are running. The detailed meaning of some of the columns (like "SZ") varies from unix to unix.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Running two processes in background

hi there, here's what i need in my korn-shell: ... begin korn-shell script ... nohup process_A.ksh ; nohup process_B.ksh & ... "other stuff" ... end lorn-shell script in plain english i want process A and process B to run in the background so that the script can continue doing... (6 Replies)
Discussion started by: jacob_gs
6 Replies

2. Programming

getting certain info for all processes currently running

i am writing a utility that displays information about all the running processes in the /proc directory. I do not know how to get the following information for each of the processes in the /proc directory: -effective user id -effective user name -effective group id -effective group name... (3 Replies)
Discussion started by: Yifan_Guo
3 Replies

3. UNIX for Dummies Questions & Answers

how to find all processes that are running

Hi i've been googling a lot but can't find an answer. All I would like to know is how to find out all processes that are running on a machine. I know ps gives all YOUR processes. thanks (9 Replies)
Discussion started by: speedieB
9 Replies

4. Programming

parsing currently running processes

Hey guys, I'm writing a monitoring program that reads the pattern and the max and min number of instances of a process and then proceeds to parse the currently running processes for the pattern. I just want to know how I should go about this. I'll give you an idea of the flow of the program:... (7 Replies)
Discussion started by: blowtorch
7 Replies

5. UNIX for Advanced & Expert Users

running processes with no hang up

Can we run a script in nohup which calls another script in nohup. eg Script1.sh #Script1 start nohup script2.sh . . . #end script1.sh Now can I do this nohup script1.sh Also is all scheduled processes (crontab entries) will run as nohup? Would appreciate if any one can... (3 Replies)
Discussion started by: yakyaj
3 Replies

6. Shell Programming and Scripting

monitoring running processes

I have a script that runs continuously and will deliver a file to multiple servers via scp. On occasions one of the scp's will hang and as a result not complete in sending the remaining files and not loop around again. If I run the scp commands with a & they'll complete, but I want to make sure... (2 Replies)
Discussion started by: nhatch
2 Replies

7. Shell Programming and Scripting

Need help with running processes script

I'm doing a script with the Shell. I need that it only show the number of running processes. Ex: echo "There are `command` running processes" Thnx! Pd: Sorry the idiom. I'm spanish. (2 Replies)
Discussion started by: Ikebana
2 Replies

8. Solaris

Running processes on GZ/LZ

Hi guys just a question is it normal to see running process on a non-global zone in the global zone... processes such as cron. (3 Replies)
Discussion started by: batas
3 Replies

9. Linux

Running processes

Hi guys is it normal to have 5-10 cron/syslog processes running... in my case i got 10 cron process running. (4 Replies)
Discussion started by: batas
4 Replies

10. Shell Programming and Scripting

Check Running Processes

I want to check how many processes are running with same names and get their respective counts. ps -ef|grep -Eo 'process1|process2|process3| '|sort -u | awk '{print $2": "$1}' Output would look like : $ ps -ef|grep -Eo 'process1|process2|process3| '|sort | uniq -c | awk '{print $2":... (8 Replies)
Discussion started by: simpltyansh
8 Replies
PS(1)							      General Commands Manual							     PS(1)

NAME
ps - process status SYNOPSIS
ps [ acgklnrtuwxU# [ core [ swap [ system ] ] ] ] DESCRIPTION
Ps prints certain indicia about active processes. To get a complete printout on the console or lpr, use ``ps axlw'' For a quick snapshot of system activity, ``ps au'' is recommended. A hyphen may precede options with no effect. The following options may be specified. a asks for information about all processes with terminals (ordinarily only one's own processes are displayed). c causes only the comm field to be displayed instead of the arguments. (The comm field is the tail of the path name of the file the process last exec'ed.) This option speeds up ps somewhat and reduces the amount of output. It is also more reliable since the process can't scribble on top of it. g asks for all processes. Without this option, ps only prints ``interesting'' processes. Processes are deemed to be uninteresting if they are process group leaders, or if their arguments begin with a `-'. This normally eliminates shells and getty processes. k causes the file /usr/sys/core is used in place of /dev/kmem and /dev/mem. This is used for postmortem system debugging. l asks for a long listing. The short listing contains the user name, process ID, tty, the cumulative execution time of the process and an approximation to the command line. n asks for numeric rather than symbolic wchans. This flag implies the ``l'' flag. r asks for ``raw'' output. A non-human readable sequence of structures is output on the standard output. There is one structure for each process, the format is defined by <psout.h> tttyname restricts output to processes whose controlling tty is the specified ttyname (which should be specified as printed by ps, including t? for processes with no tty). This option must be the last one given. u A user oriented output is produced. This includes the name of the owner of the process, process id, nice value, size, tty, cpu time used, and the command. w tells ps you are on a wide terminal (132 columns). Ps normally assumes you are on an 80 column terminal. This information is used to decide how much of long commands to print. The w option may be repeated, e.g. ww, and the entire command, up to 128 characters, will be printed without regard to terminal width. x asks even about processes with no terminal. U causes ps to update a private database where is keeps system information. Thus ``ps -U'' should be included in the /etc/rc file. # A process number may be given, (indicated here by #), in which case the output is restricted to that process. This option must also be last. A second argument tells ps where to look for core if the k option is given, instead of /usr/sys/core. A third argument is the name of a swap file to use instead of the default /dev/swap. If a fourth argument is given, it is taken to be the file containing the system's namelist. Otherwise, ``/unix'' is used. The output is sorted by tty, then by process ID. The long listing is columnar and contains F Flags associated with the process. These are defined by #define lines in /usr/include/sys/proc.h. S The state of the process. 0: nonexistent; S: sleeping; W: waiting; R: running; I: intermediate; Z: terminated; T: stopped. UID The user id of the process owner. PID The process ID of the process; as in certain cults it is possible to kill a process if you know its true name. PPID The process ID of the parent process. CPU Processor utilization for scheduling. PRI The priority of the process; high numbers mean low priority. NICE Used in priority computation. ADDR The memory address of the process if resident, otherwise the disk address. SZ The size in blocks (512 bytes) of the memory image of the process. WCHAN The event for which the process is waiting or sleeping; if blank, the process is running. TTY The controlling tty for the process. TIME The cumulative execution time for the process. COMMAND The command and its arguments. A process that has exited and has a parent, but has not yet been waited for by the parent is marked <defunct>. Ps makes an educated guess as to the file name and arguments given when the process was created by examining memory or the swap area. The method is inherently some- what unreliable and in any event a process is entitled to destroy this information, so the names cannot be counted on too much. FILES
/unix system namelist /dev/kmem kernel memory /dev/swap swap device /usr/sys/core core file /dev searched to find swap device and tty names /var/run/psdatabase system namelist and device information SEE ALSO
kill(1), w(1), pstat(8) BUGS
Things can change while ps is running; the picture it gives is only a close approximation to reality. Some processes, typically those in the background, are printed with null or garbaged arguments, even though the process has not swapped. (Sometimes ps even loses on its own arguments!) In these cases, the name of the command is printed in parentheses. When automatic crash dumps are enabled, /usr/sys/core is not a sensible default core file name. 3rd Berkeley Distribution PS(1)
All times are GMT -4. The time now is 04:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy