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