|PS(1)||FreeBSD General Commands Manual||PS(1)|
NAMEps — process status
|ps||[ -aCcdefHhjlmrSTuvwXxZ][ -O fmt | -o fmt][ -G gid[ , gid...]][ -J jid[ , jid...]][ -M core][ -N system][ -p pid[ , pid...]][ -t tty[ , tty...]][ -U user[ , user...]]|
DESCRIPTIONThe ps utility displays a header line, followed by lines containing information about all of your processes that have controlling terminals. If the -x options is specified, ps will also display processes that do not have controlling terminals.
A different set of processes can be selected for display by using any combination of the -a, -G, -J, -p, -T, -t, and -U options. If more than one of these options are given, then ps will select all processes which are matched by at least one of the given options.
For the processes which have been selected for display, ps will usually display one line per process. The -H option may result in multiple output lines (one line per thread) for some processes. By default all of these output lines are sorted first by controlling terminal, then by process ID. The -m, -r, -u, and -v options will change the sort order. If more than one sorting option was given, then the selected processes will be sorted by the last sorting option which was specified.
For the processes which have been selected for display, the information to display is selected based on a set of keywords (see the -L, -O, and -o options). The default output format includes, for each process, the process' ID, controlling terminal, state, CPU time (including both user and system time) and associated command.
The options are as follows:
- Display information about other users' processes as well as your own. If the security.bsd.see_other_uids sysctl is set to zero, this option is honored only if the UID of the user is 0.
- Change the “command” column output to just contain the executable name, rather than the full command line.
- Change the way the CPU percentage is calculated by using a “raw” CPU calculation that ignores “resident” time (this normally has no effect).
- Arrange processes into descendancy order and prefix each command with indentation text showing sibling and parent/child relationships. If either of the -m and -r options are also used, they control how sibling processes are sorted relative to each other. Note that this option has no effect if the “command” column is not the last column displayed.
- Display the environment as well.
- Show commandline and environment information about swapped out processes. This option is honored only if the UID of the user is 0.
- Display information about processes which are running with the specified real group IDs.
- Show all of the kernel visible threads associated with each process. Depending on the threading package that is in use, this may show only the process, only the kernel scheduled entities, or all of the process threads.
- Repeat the information header as often as necessary to guarantee one header per page of information.
- Print information associated with the following keywords: user, pid, ppid, pgid, sid, jobc, state, tt, time, and command.
- Display information about processes which match the specified jail IDs. This may be either the jid or name of the jail. Use -J 0 to display only host processes. This flag implies -x by default.
- List the set of keywords available for the -O and -o options.
- Display information associated with the following keywords: uid, pid, ppid, cpu, pri, nice, vsz, rss, mwchan, state, tt, time, and command.
- Extract values associated with the name list from the specified core instead of the currently running system.
- Sort by memory usage, instead of the combination of controlling terminal and process ID.
- Extract the name list from the specified system instead of the default, which is the kernel image the system has booted from.
Add the information associated with the space or comma separated list of keywords specified, after the process ID, in the default information display. Keywords may be appended with an equals (‘
=’) sign and a string. This causes the printed header to use the specified string instead of the standard header.
Display information associated with the space or comma separated list of keywords specified. The last keyword in the list may be appended with an equals (‘
=’) sign and a string that spans the rest of the argument, and can contain space and comma characters. This causes the printed header to use the specified string instead of the standard header. Multiple keywords may also be given in the form of more than one -o option. So the header texts for multiple keywords can be changed. If all keywords have empty header texts, no header line is written.
- Display information about processes which match the specified process IDs.
- Sort by current CPU usage, instead of the combination of controlling terminal and process ID.
- Change the way the process times, namely cputime, systime, and usertime, are calculated by summing all exited children to their parent process.
- Display information about processes attached to the device associated with the standard input.
- Display information about processes attached to the specified terminal devices. Full pathnames, as well as abbreviations (see explanation of the tt keyword) can be specified.
- Display the processes belonging to the specified usernames.
- Display information associated with the following keywords: user, pid, %cpu, %mem, vsz, rss, tt, state, start, time, and command. The -u option implies the -r option.
- Display information associated with the following keywords: pid, state, time, sl, re, pagein, vsz, rss, lim, tsiz, %cpu, %mem, and command. The -v option implies the -m option.
- Use 132 columns to display information, instead of the default which is your window size. If the -w option is specified more than once, ps will use as many columns as necessary without regard for your window size. Note that this option has no effect if the “command” column is not the last column displayed.
- When displaying processes matched by other options, skip any processes which do not have a controlling terminal. This is the default behaviour.
- When displaying processes matched by other options, include processes which do not have a controlling terminal. This is the opposite of the -X option. If both -X and -x are specified in the same command, then ps will use the one which was specified last.
- Add mac(4) label to the list of keywords for which ps will display information.
A complete list of the available keywords are listed below. Some of these keywords are further specified as follows:
- The CPU utilization of the process; this is a decaying average over up to a minute of previous (real) time. Since the time base over which this is computed varies (since processes may be very young) it is possible for the sum of all %cpu fields to exceed 100%.
- The percentage of real memory used by this process.
- Login class associated with the process.
The flags associated with the process as in the include file
P_ADVLOCK 0x00001 Process may hold a POSIX advisory lock P_CONTROLT 0x00002 Has a controlling terminal P_KTHREAD 0x00004 Kernel thread P_FOLLOWFORK 0x00008 Attach debugger to new children P_PPWAIT 0x00010 Parent is waiting for child to exec/exit P_PROFIL 0x00020 Has started profiling P_STOPPROF 0x00040 Has thread in requesting to stop prof P_HADTHREADS 0x00080 Has had threads (no cleanup shortcuts) P_SUGID 0x00100 Had set id privileges since last exec P_SYSTEM 0x00200 System proc: no sigs, stats or swapping P_SINGLE_EXIT 0x00400 Threads suspending should exit, not wait P_TRACED 0x00800 Debugged process being traced P_WAITED 0x01000 Someone is waiting for us P_WEXIT 0x02000 Working on exiting P_EXEC 0x04000 Process called exec P_WKILLED 0x08000 Killed, shall go to kernel/user boundary ASAP P_CONTINUED 0x10000 Proc has continued from a stopped state P_STOPPED_SIG 0x20000 Stopped due to SIGSTOP/SIGTSTP P_STOPPED_TRACE 0x40000 Stopped because of tracing P_STOPPED_SINGLE 0x80000 Only one thread can continue P_PROTECTED 0x100000 Do not kill on memory overcommit P_SIGEVENT 0x200000 Process pending signals changed P_SINGLE_BOUNDARY 0x400000 Threads should suspend at user boundary P_HWPMC 0x800000 Process is using HWPMCs P_JAILED 0x1000000 Process is in jail P_INEXEC 0x4000000 Process is in execve() P_STATCHILD 0x8000000 Child process stopped or exited P_INMEM 0x10000000 Loaded into memory P_SWAPPINGOUT 0x20000000 Process is being swapped out P_SWAPPINGIN 0x40000000 Process is being swapped in P_PPTRACE 0x80000000 Vforked child issued ptrace(PT_TRACEME)
The flags kept in
p_flag2 associated with the process as in the include file
P2_INHERIT_PROTECTED 0x00000001 New children get P_PROTECTED
- The MAC label of the process.
- The soft limit on memory used, specified via a call to setrlimit(2).
The exact time the command started, using the ‘
%c’ format described in strftime(3).
- The name of the lock that the process is currently blocked on. If the name is invalid or unknown, then “???” is displayed.
- The login name associated with the session the process is in (see getlogin(2)).
- The event name if the process is blocked normally, or the lock name if the process is blocked on a lock. See the wchan and lockname keywords for details.
- The process scheduling increment (see setpriority(2)).
- the real memory (resident set) size of the process (in 1024 byte units).
The time the command started. If the command started less than 24 hours ago, the start time is displayed using the “
%l:ps.1p” format described in strftime(3). If the command started less than 7 days ago, the start time is displayed using the “
%a6.15p” format. Otherwise, the start time is displayed using the “
The state is given by a sequence of characters, for example, “
RWNA”. The first character indicates the run state of the process:
- Marks a process in disk (or other short term, uninterruptible) wait.
- Marks a process that is idle (sleeping for longer than about 20 seconds).
- Marks a process that is waiting to acquire a lock.
- Marks a runnable process.
- Marks a process that is sleeping for less than about 20 seconds.
- Marks a stopped process.
- Marks an idle interrupt thread.
- Marks a dead process (a “zombie”).
Additional characters after these, if any, indicate additional state information:
- The process is in the foreground process group of its control terminal.
- The process has raised CPU scheduling priority.
- The process is trying to exit.
- Marks a process which is in jail(2). The hostname of the prison can be found in /proc/< pid> /status.
- The process has pages locked in core (for example, for raw I/O).
- The process has reduced CPU scheduling priority (see setpriority(2)).
- The process is a session leader.
- The process is suspended during a vfork(2).
- The process is swapped out.
- The process is being traced or debugged.
An abbreviation for the pathname of the controlling terminal, if any. The abbreviation consists of the three letters following
/dev/tty, or, for pseudo-terminals, the corresponding entry in
/dev/pts. This is followed by a ‘
-’ if the process can no longer reach that controlling terminal (i.e., it has been revoked). A ‘
-’ without a preceding two letter abbreviation or pseudo-terminal device number indicates a process which never had a controlling terminal. The full pathname of the controlling terminal is available via the tty keyword.
- The event (an address in the system) on which a process waits. When printed numerically, the initial part of the address is trimmed off and the result is printed in hex, for example, 0x80324000 prints as 324000.
When printing using the command keyword, a process that has exited and has a parent that has not yet waited for the process (in other words, a zombie) is listed as “
<defunct>”, and a process which is blocked while trying to exit is listed as “
<exiting>”. If the arguments cannot be located (usually because it has not been set, as is the case of system processes and/or kernel threads) the command name is printed within square brackets. The ps utility first tries to obtain the arguments cached by the kernel (if they were shorter than the value of the kern.ps_arg_cache_limit sysctl). The process can change the arguments shown with setproctitle(3). Otherwise, 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 somewhat unreliable and in any event a process is entitled to destroy this information. The ucomm (accounting) keyword can, however, be depended on. If the arguments are unavailable or do not agree with the ucomm keyword, the value for the ucomm keyword is appended to the arguments in parentheses.
KEYWORDSThe following is a complete list of the available keywords and their meanings. Several of them have aliases (keywords which are synonyms).
- percentage CPU usage (alias pcpu)
- percentage memory usage (alias pmem)
- accounting flag (alias acflg)
- command and arguments
- login class
- command and arguments
- number of copy-on-write faults
- short-term CPU usage factor (for scheduling)
- data size (in Kbytes)
- system-call emulation environment
- elapsed running time, format [ days-][ hours:]minutes:seconds.
- elapsed running time, in decimal integer seconds
- default FIB number, see setfib(1)
- the process flags, in hexadecimal (alias f)
- the additional set of process flags, in hexadecimal (alias f2)
- effective group ID (alias egid)
- group name (from egid) (alias egroup)
- total blocks read (alias inblock)
- jail ID
- job control count
- tracing flags
- MAC label
- memoryuse limit
- lock currently blocked on (as a symbolic name)
- login name of user who started the session
- time started
- process thread-id
- total page faults
- total page reclaims
- total messages received (reads from pipes/sockets)
- total messages sent (writes on pipes/sockets)
- wait channel or lock currently blocked on
- nice value (alias ni)
- total involuntary context switches
- number of threads tied to a process
- total signals taken (alias nsignals)
- total swaps in/out
- total voluntary context switches
- wait channel (as an address)
- total blocks written (alias oublock)
- process pointer
- pageins (same as majflt)
- process group number
- process ID
- parent process ID
- scheduling priority
- core residency time (in seconds; 127 = infinity)
- real group ID
- group name (from rgid)
- resident set size
- realtime priority (101 = not a realtime process)
- real user ID
- user name (from ruid)
- session ID
- pending signals (alias pending)
- caught signals (alias caught)
- ignored signals (alias ignored)
- blocked signals (alias blocked)
- sleep time (in seconds; 127 = infinity)
- stack size (in Kbytes)
- time started
- symbolic process state (alias stat)
- saved gid from a setgid executable
- saved UID from a setuid executable
- accumulated system CPU time
- thread address
- control terminal device number
- accumulated CPU time, user + system (alias cputime)
- control terminal process group ID
- control terminal session ID
- text size (in Kbytes)
- control terminal name (two letter abbreviation)
- full name of control terminal
- name to be used for accounting
- effective user ID (alias euid)
- scheduling priority on return from system call (alias usrpri)
- process pointer
- user name (from UID)
- accumulated user CPU time
- virtual size in Kbytes (alias vsize)
- wait channel (as a symbolic name)
- exit or stop status (valid only for stopped or zombie process)
Note that the pending column displays bitmask of signals pending in the process queue when -H option is not specified, otherwise the per-thread queue of pending signals is shown.
ENVIRONMENTThe following environment variables affect the execution of ps:
- If set, specifies the user's preferred output width in column positions. By default, ps attempts to automatically determine the terminal width.
- default system namelist
EXAMPLESDisplay information on all system processes:
$ ps -auxw
SEE ALSOkill(1), pgrep(1), pkill(1), procstat(1), w(1), kvm(3), strftime(3), mac(4), procfs(5), pstat(8), sysctl(8), mutex(9)
STANDARDSFor historical reasons, the ps utility under FreeBSD supports a different set of options from what is described by IEEE Std 1003.2 (“POSIX.2”), and what is supported on non- BSD operating systems.
HISTORYThe ps command appeared in Version 4 AT&T UNIX.
BUGSSince ps cannot run faster than the system and is run as any other scheduled process, the information it displays can never be exact.
The ps utility does not correctly display argument lists containing multibyte characters.
|August 7, 2014||FreeBSD|