.\" Copyright (c) 1980, 1990, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
.\" %sccs.include.redist.man%
.\" @(#)w.1 8.1 (Berkeley) %G%
.Nd "who present users are and what they are doing"
utility prints a summary of the current activity on the system,
including what each user is doing.
The first line displays the current time of day, how long the system has
been running, the number of users logged into the system, and the load
The load average numbers give the number of jobs in the run queue averaged
over 1, 5 and 15 minutes.
The fields output are the user's login name, the name of the terminal the
user is on, the host from which the user is logged in, the time the user
logged on, the time since the user last typed anything,
and the name and arguments of the current process.
The options are as follows:
Output is sorted by idle time.
Extract values associated with the name list from the specified
core instead of the default
Extract the name list from the specified system instead of the
Show network addresses as numbers (normally
interprets addresses and attempts to display them symbolically).
name is specified, the output is restricted to that user.
.Bl -tag -width /var/run/utmp -compact
list of users on the system
The current algorithm is ``the highest numbered process on the terminal
that is not ignoring interrupts, or, if there is none, the highest numbered
process on the terminal''.
This fails, for example, in critical sections of programs like the shell
and editor, or when faulty programs running in the background fork and fail
(In cases where no process can be found,
time is only an estimate, in particular, if someone leaves a background
process running after logging out, the person currently on that terminal is
Background processes are not shown, even though they account for
much of the load on the system.
Sometimes processes, typically those in the background, are printed with
null or garbaged arguments.
In these cases, the name of the command is printed in parentheses.
utility does not know about the new conventions for detection of background
It will sometimes find a background job instead of the right one.
flags are no longer supported.