1 .\" Copyright (c) 1989, 1990, 1993, 1994
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
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.
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
32 .\" @(#)finger.1 8.3 (Berkeley) 5/5/94
40 .Nd user information lookup program
45 .Op Ar user@host ...\&
49 utility displays information about the system users.
52 .Bl -tag -width indent
56 to use IPv4 addresses only.
60 to use IPv6 addresses only.
62 Display the user's login name, real name, terminal name and write
63 status (as a ``*'' before the terminal name if write permission is
64 denied), idle time, login time, and either office location and office
65 phone number, or the remote host.
68 is given, the office location and office phone number is printed
72 is given, the remote host is printed instead.
74 Idle time is in minutes if it is a single integer, hours and minutes
75 if a ``:'' is present, or days if a ``d'' is present.
78 the login time indicates the time of last login.
79 Login time is displayed as the day name if less than 6 days, else month, day;
80 hours and minutes, unless more than six months ago, in which case the year
81 is displayed rather than the hours and minutes.
83 Unknown devices as well as nonexistent idle and login times are
84 displayed as single asterisks.
86 When used in conjunction with the
88 option, the name of the remote host is displayed instead of the office
89 location and office phone.
91 When used in conjunction with the
93 option, the office location and office phone information is displayed
94 instead of the name of the remote host.
96 This option restricts the gecos output to only the users' real
98 It also has the side-effect of restricting the output
99 of the remote host when used in conjunction with the
106 Produce a multi-line format displaying all of the information
109 option as well as the user's home directory, home phone number, login
110 shell, mail status, and the contents of the files
116 from the user's home directory.
118 If idle time is at least a minute and less than a day, it is
119 presented in the form ``hh:mm''.
120 Idle times greater than a day are presented as ``d day[s]hh:mm''.
122 Phone numbers specified as eleven digits are printed as ``+N-NNN-NNN-NNNN''.
123 Numbers specified as ten or seven digits are printed as the appropriate
124 subset of that string.
125 Numbers specified as five digits are printed as ``xN-NNNN''.
126 Numbers specified as four digits are printed as ``xNNNN''.
128 If write permission is denied to the device, the phrase ``(messages off)''
129 is appended to the line containing the device name.
130 One entry per user is displayed with the
132 option; if a user is logged on multiple times, terminal information
133 is repeated once per login.
135 Mail status is shown as ``No Mail.'' if there is no mail at all, ``Mail
136 last read DDD MMM ## HH:MM YYYY (TZ)'' if the person has looked at their
137 mailbox since new mail arriving, or ``New mail received ...'', ``Unread
138 since ...'' if they have new mail.
145 from displaying the contents of the
157 is usually a login name; however, matching will also be done on the
158 users' real names, unless the
161 All name matching performed by
165 Disable the piggybacking of data on the initial connection request.
166 This option is needed to finger hosts with a broken TCP implementation.
169 If no options are specified,
173 style output if operands are provided, otherwise to the
176 Note that some fields may be missing, in either format, if information
177 is not available for them.
179 If no arguments are specified,
181 will print an entry for each user currently logged into the system.
185 utility may be used to look up users on a remote machine.
186 The format is to specify a
192 where the default output
193 format for the former is the
195 style, and the default output format for the latter is the
200 option is the only option that may be passed to a remote machine.
204 exists in the user's home directory,
206 behaves as if the user in question does not exist.
210 configuration file can be used to specify aliases.
215 aliases will work for both local and network queries.
219 utility utilizes the following environment variable, if it exists:
222 This variable may be set with favored options to
226 .Bl -tag -width /var/log/lastlog -compact
227 .It Pa /etc/finger.conf
228 alias definition data base
229 .It Pa /var/log/lastlog
240 .%T The Finger User Information Protocol
250 The current FINGER protocol RFC requires that the client keep the connection
251 fully open until the server closes.
252 This prevents the use of the optimal
253 three-packet T/TCP exchange.
254 (Servers which depend on this requirement are
255 bogus but have nonetheless been observed in the Internet at large.)
259 utility does not recognize multibyte characters.