
finger <username[@host]> [<username[@host]> ...]

        Issue a network 'finger' request for <username> at <host>.
        Finger is typically used to find out specific information about
        users on local or remote hosts.  By fingering a user, you can
        find out such information as a user's name, his mailing address,
        telephone number, QSL information, and other useful facts.  This
        information is kept in a separate text file for each user.

        As our network expands, this application will help hams find out
        information about each other quickly and efficiently.

        The finger command under NOS can be issued in any of the
        following three ways:

          finger <username>           >> Examples: finger n8fow
          finger <username>@<host>                 finger n8fow@n8fow
          finger @<host>                           finger @n8fow

        The first form of the command is used to find out information
        about a user at the local host, namely your own system.  It is
        useful for testing 'finger' on a system that you know is running.

        The second form of the command is used to find out information
        about a user at a remote host.

        If you don't know the name of a particular user at a remote host,
        you can use the third form of the command.  This command returns
        a list of all 'finger' files on the remote system.

        To enable the finger server so that others may query the users on
        your system, you must give the 'start finger' command.  The finger
        files that provide information on a <username> are located by
        default in \finger (see Fdir and Fdbase in nos.cfg), and are
        ordinary ASCII files created by the sysop.  Also, if the SAM or
        QRZ callbook server is configured, <username> is looked up in the
        callbook and displayed if the search is successful.

        Certain <username> strings are taken to mean that a Jnos function
        should be invoked to display system information, depending on
        what configuration options were used to build the server Jnos:

        <username>      config_opt      output_same_as

        conf            CONVERS         conference bridge /WHO
        links           CONVERS         conference bridge /LINKS
        mbxinfo         MAILBOX         'I cmd in mailbox'
        mhold           HOLD_LOCAL_MSGS 'mbox holdlocal'
        mstat           MAILBOX         'mbox mailstat' 
        mpast           MAILBOX         'mbox past'
        users           MAILBOX         'mbox status'
        usersdat        USERLOG         'finger x' forall users in users.dat
        mailfor         MAILFOR         'mbox mailfor'
        info            ALLCMD          'info'
        ax25            AX25            'ax25 stat'
        aheard          AX25            'ax25 heard'
        netrom          NETROM          'netrom stat'
        iheard          all             'ip heard'
        memstat         all             'mem stat'
        socket          all             'socket'
        tcpview         all             'tcp view bytes'
        asystat         ASY             'asystat'
        pkstat          PACKET          'pkstat'
        rip             RIP             'rip stat'

