1in.fingerd(1M)          System Administration Commands          in.fingerd(1M)
2
3
4

NAME

6       in.fingerd, fingerd - remote user information server
7

SYNOPSIS

9       /usr/sbin/in.fingerd
10
11

DESCRIPTION

13       fingerd  implements the server side of the Name/Finger protocol, speci‐
14       fied in RFC 742. The Name/Finger protocol provides a  remote  interface
15       to  programs  which display information on system status and individual
16       users. The protocol imposes little  structure  on  the  format  of  the
17       exchange  between  client and server. The client provides a single com‐
18       mand line to the finger server which returns a printable reply.
19
20
21       fingerd waits for connections on TCP port 79. Once connected, it  reads
22       a  single  command  line  terminated  by RETURN-LINEFEED and passes the
23       arguments to finger(1), prepended with -s. fingerd closes  its  connec‐
24       tions as soon as the output is finished.
25

FILES

27       /var/adm/utmpx      User and accounting information.
28
29
30       /etc/passwd         System password file.
31
32
33       /var/adm/lastlog    Last login times.
34
35
36       $HOME/.plan         User's plans.
37
38
39       $HOME/.project      User's projects.
40
41

USAGE

43       fingerd and in.fingerd are IPv6-enabled. See ip6(7P).
44

ATTRIBUTES

46       See attributes(5) for descriptions of the following attributes:
47
48
49
50
51       ┌─────────────────────────────┬─────────────────────────────┐
52       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
53       ├─────────────────────────────┼─────────────────────────────┤
54       │Availability                 │SUNWrcmds                    │
55       └─────────────────────────────┴─────────────────────────────┘
56

SEE ALSO

58       finger(1),  svcs(1), inetadm(1M), inetd(1M), svcadm(1M), attributes(5),
59       smf(5), ip6(7P)
60
61
62       Harrenstien, Ken, RFC 742, NAME/FINGER,   Network  Information  Center,
63       SRI International, Menlo Park, Calif., December 1977.
64

NOTES

66       Connecting  directly  to  the  server  from a TIP or an equally narrow-
67       minded TELNET-protocol user program can result in meaningless  attempts
68       at  option negotiation being sent to the server, which foul up the com‐
69       mand line interpretation. fingerd should be taught to filter out  IAC's
70       and  perhaps even respond negatively (IAC does not)  to all option com‐
71       mands received.
72
73
74       The in.fingerd service is managed by the service  management  facility,
75       smf(5), under the service identifier:
76
77         svc:/network/finger:default
78
79
80
81
82       Administrative actions on this service, such as enabling, disabling, or
83       requesting restart, can be performed using  svcadm(1M).  Responsibility
84       for  initiating  and restarting this service is delegated to inetd(1M).
85       Use inetadm(1M) to make configuration changes and to view configuration
86       information for this service. The service's status can be queried using
87       the svcs(1) command.
88
89
90
91SunOS 5.11                        31 Jul 2004                   in.fingerd(1M)
Impressum