386BSD 0.1 development
[unix-history] / usr / src / usr.bin / w / w.1
CommitLineData
14253b29
WJ
1.\" Copyright (c) 1980, 1990, 1991 Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\" must display the following acknowledgement:
14.\" This product includes software developed by the University of
15.\" California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)w.1 6.8 (Berkeley) 4/23/91
33.\"
34.Dd April 23, 1991
35.Dt W 1
36.Os BSD 4
37.Sh NAME
38.Nm w
39.Nd "who present users are and what they are doing"
40.Sh SYNOPSIS
41.Nm w
42.Op Fl hi
43.Op Ar user
44.Sh DESCRIPTION
45.Nm W
46prints a summary of the current activity on the system,
47including what each user is doing.
48The heading shows the current time of day, how long the system has been up,
49the number of users logged into the system, and the load averages.
50The load average numbers give the number of jobs in the run queue
51averaged over 1, 5 and 15 minutes.
52.Pp
53The fields output are:
54the user's login name, the name of the terminal (tty) the user is on,
55the host from which the user is logged in, the time the user logged on,
56the time since the user last typed anything,
57the
58.Tn CPU
59time used by all processes and their children on that tty,
60the
61.Tn CPU
62time used by the currently active processes, and the name and arguments
63of the current process.
64.Pp
65Available options are:
66.Bl -tag -width Ds
67.It Fl h
68Suppress the heading.
69.It Fl i
70Output is sorted by idle time.
71.El
72.Pp
73If a
74.Ar user
75name is given, the output is restricted to that user.
76.Sh FILES
77.Bl -tag -width /var/run/utmp -compact
78.It Pa /var/run/utmp
79list of users on the system
80.El
81.Sh SEE ALSO
82.Xr who 1 ,
83.Xr finger 1 ,
84.Xr ps 1
85.Sh BUGS
86The notion of the
87.Dq current process
88is muddy.
89The current algorithm is ``the highest numbered process on the terminal that
90is not ignoring interrupts, or, if there is none, the highest numbered
91process on the terminal''.
92This fails, for example, in critical sections of programs like the shell
93and editor, or when faulty programs running in the background fork and fail
94to ignore interrupts.
95(In cases where no process can be found,
96.Nm w
97prints
98.Dq \- . )
99.Pp
100The
101.Tn CPU
102time is only an estimate, in particular, if someone leaves a
103background process running after logging out, the person currently
104on that terminal is
105.Dq charged
106with the time.
107.Pp
108Background processes are not shown, even though they account for
109much of the load on the system.
110.Pp
111Sometimes processes, typically those in the background, are
112printed with null or garbaged arguments.
113In these cases, the name of the command is printed in parentheses.
114.Pp
115.Nm W
116does not know about the new conventions for detection of background jobs.
117It will sometimes find a background job instead of the right one.
118.Sh COMPATIBILITY
119The
120.Fl f ,
121.Fl l ,
122.Fl s ,
123and
124.Fl w
125flags are no longer supported.
126.Sh HISTORY
127The
128.Nm
129command appeared in
130.Ux 3.0 .