1.\" $NetBSD: w.1,v 1.18 2005/01/11 09:39:12 wiz 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 January 11, 2005 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 hinw 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. 54.Pp 55The fields output are the user's login name, the name of the terminal the 56user is on, the host from which the user is logged in, the time the user 57logged on, the time since the user last typed anything, 58and the name and arguments of the current process. 59.Pp 60The options are as follows: 61.Bl -tag -width Ds 62.It Fl h 63Suppress the heading. 64.It Fl i 65Output is sorted by idle time. 66.It Fl M 67Extract values associated with the name list from the specified 68core instead of the default 69.Dq /dev/kmem . 70.It Fl N 71Extract the name list from the specified system instead of the 72default 73.Dq /netbsd . 74.It Fl n 75Show network addresses as numbers (normally 76.Nm 77interprets addresses and attempts to display them symbolically). 78.It Fl w 79Show wide output without truncating any fields. 80.El 81.Pp 82If a 83.Ar user 84name is specified, the output is restricted to that user. 85.Sh FILES 86.Bl -tag -width /var/run/utmp -compact 87.It Pa /var/run/utmp 88list of users on the system 89.El 90.Sh SEE ALSO 91.Xr finger 1 , 92.Xr ps 1 , 93.Xr uptime 1 , 94.Xr who 1 95.Sh HISTORY 96The 97.Nm 98command appeared in 99.Bx 3.0 . 100.Sh BUGS 101The notion of the 102.Dq current process 103is muddy. 104The current algorithm is ``the highest numbered process on the terminal 105that is not ignoring interrupts, or, if there is none, the highest numbered 106process on the terminal''. 107This fails, for example, in critical sections of programs like the shell 108and editor, or when faulty programs running in the background fork and fail 109to ignore interrupts. 110(In cases where no process can be found, 111.Nm 112prints 113.Dq \- . ) 114.Pp 115Background processes are not shown, even though they account for 116much of the load on the system. 117.Pp 118Sometimes processes, typically those in the background, are printed with 119null or garbaged arguments. 120In these cases, the name of the command is printed in parentheses. 121.Pp 122The 123.Nm 124utility does not know about the new conventions for detection of background 125jobs. 126It will sometimes find a background job instead of the right one. 127