home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.admin
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!ra!hp8c.nrl.navy.mil!bgarrett
- From: bgarrett@hp8c.nrl.navy.mil (Brian S. Garrett)
- Subject: Re: Question on finger
- Message-ID: <By6ytE.JLF@ra.nrl.navy.mil>
- Sender: usenet@ra.nrl.navy.mil
- Organization: Naval Research Lab, Washington, DC
- References: <1992Nov20.175846.17994@eng.ufl.edu>
- Distribution: usa
- Date: Mon, 23 Nov 1992 23:05:38 GMT
- Lines: 36
-
-
- In article <1992Nov20.175846.17994@eng.ufl.edu>, eric@joker.mil.ufl.edu (Eric M. Schwartz) writes:
- > I am having a problem with the finger command when used from a remote machine
- > to my machine. If on a remote machine and a finger to my machine is attempted,
- > the result is just my machine address. For example:
- >
- > > finger eric@mil.ufl.edu
- >
- > results in the following
- >
- > > [mil.ufl.edu]
- > >
- > My /etc/passwd seems to be alright. I don't know if this is relevant, but
- > my machine is a Silicon Graphics 4D/20 with a System V Release 3.2 operating
- > system.
- >
-
- fingerd is the server for the RFC 742 Name/Finger protocol. It
- provides a network interface to finger(1), which gives a status report
- of users currently logged in on the system or a detailed report about
- a specific user. The Internet daemon executes fingerd when it
- receives a service request at the port listed in the services data
- base for ``finger'' using ``tcp'' protocol; see inetd(1m) and
- services(4).
-
- Check your /etc/inetd.conf as well as your /etc/services file.
-
-
- Brian S. Garrett
- bgarrett@hp8c.nrl.navy.mil
-
-
- ----------
- "It is impossible to enjoy idling thoroughly
- unless one has plenty of work to do."
- - J K Jerome
-