---------------------------------------
 OS/2 Presentation Manager
     TCP/IP Finger Daemon v1.0c
 for TCP/IP v2.0, v3.0 or Warp Connect
 Copyright (c) 1995 Amilcar M. Ubiera
- - - - - - - - - - - - - - - - - - - -
by Amilcar Ubiera
   amubiera@eos.ncsu.edu
- - - - - - - - - - - - - - - - - - - -
last updated 12/05/95
---------------------------------------

Since OS/2 TCP/IP 2.0 nor OS/2 Connect came with a Finger Daemon, I decided
to charge ahead and make one.

This simple server lets the operating system identify itself with the user
that is currently using the machine. Unlike UNIX systems, OS/2 is a single
user operating system, therefore, not having any native user listing features
of the currently logged on users.

-------------------------
 I N S T R U C T I O N S
-------------------------

I. INSTALLING THE FINGER SERVER
   All you need to do is unzip the archive and
   put the files into a directory in your path.
   There is no INSTALL executable, just run
   PMFD.EXE .

II. HOW TO USE THE SERVER
   1. ADDING A USER
      The first time you run PMFD the user list will be empty.
      To add a user just click the 'Add User' button. A dialog
      window will ask you for the user ID to be added.  The user
      will be then added to the 'User Select List.'

      No checking is done on the text you input, so watch
      out what kind of characters you put in there, I haven't
      tried everything yet.  :)

      The maximum number of users that can be added is 256 for
      this version of the daemon.  And the maximum number of
      characters for the ID is 32 characters long.

   2. DELETING A USER
      To delete the currently highlighted user, simple click
      the 'Delete User' button.

   3. SELECTING A USER
      To select a user, simply click on the user ID from the
      'User Select List.'  Once the user is selected, the
      server will show this user to the clients inquiring
      finger information.

        e.g.   Suppose you have one user with ID 'Amilcar' already
               added and highlighted. When some remote client
               tries to connect he/she will see:

               unix% finger @helkyn.catt.ncsu.edu
               [helkyn.catt.ncsu.edu]
               Login Name
               Amilcar is logged-on

        e.g.   or if the remote client typed:

               unix% finger Amilcar@helkyn.catt.ncsu.edu
               [helkyn.catt.ncsu.edu]
               Login name: Amilcar
               In real life: Amilcar M. Ubiera
               Office: 502D Wood Hall NCSU
               Phone: (919)-512-6755

                --logged on--

               Plan:

                --none--

   4. HIDING THE USER
      Once a user is selected, the server will show this user
      as I mentioned in section 3.  But if you're working on
      some heavy duty deadlined project, and you don't want
      people to know you're on-line, just click on the
      'User is Hidden' check box and the server will always
      respond with:

               unix% finger @helkyn.catt.ncsu.edu
               [helkyn.catt.ncsu.edu]
               Login Name
               no one is logged-on

      until you uncheck the check box again.

   5. CONFIGURING A USER
      To configure the user information just select a user
      you want to configure and click on the 'Configure'
      button.  A dialog box will show up with the configuration
      information for the current user.  The fields that can
      be modified are as follows:

               Login name:           <-- login ID
               Office:               <-- office where user is located
               Real Name:            <-- the users real name
               Phone No.:            <-- the users phone number
               Plan file location:   <-- .plan file for the user (as in unix)
               Idle timeout:         <-- time to logoff user after # min idle

      These fields can be changed as you wish and they will immediately
      reflect the output a client gets.

      The plan file will be shown after all the other information has
      been sent to the remote connection.  This file should be a plain
      ASCII file, preferably ending in .PLN for consistency.

   6. EXITING THE SERVER
      To shutdown the finger server, simply click on the 'Exit'
      button.  The TCP/IP socket will be closed, and fingers will no
      longer be serviced.

   7. GETTING ABOUT INFORMATION
      To get info on the server and the author, just click on
      the 'About' button and a dialog box will pop-up with
      the daemon version, my name and e-mail address for contact info.

   8. PMFD.INI <-- what about it?
      So that there is no mystery, here is the structure on PMFD.INI
         <INDEX OF SELECTED USER> <RETURN>
         <USER1 LOGIN_ID> <RETURN>
         <USER1 OFFICE> <RETURN>
         <USER1 PHONE#> <RETURN>
         <USER1 PLANFILE> <RETURN>
         <USER1 TIMEOUT> <RETURN>
         <RETURN>
         <USER2 LOGIN_ID> <RETURN>
         <USER2 OFFICE> <RETURN>
         <USER2 PHONE#> <RETURN>
         <USER2 PLANFILE> <RETURN>
         <USER2 TIMEOUT> <RETURN>
         <RETURN>
                 .
                 .
                 .

      If you mangle the PMFD.INI, the program will behave strangely,
      as I have experimented with it.  So just let the program do
      what it needs to do, unless you follow the structure that I
      show above.

III. INCOMING FINGERS LIST
   This list shows the IP address, time and date of the clients
   that have connected to the server.

   For example, if you running the server and a machine with IP address
   152.1.43.4 was looking for finger info, you will see the following
   show up:
               Incoming Fingers --------
               152.1.43.4  16:06(11-28)
               152.1.43.4  15:55(11-28)

   This person fingered your machine at 4:06PM November 28 of this year.
   And previously at 3:55 of the same day.
   As the incoming fingers arrive, the most recent ones will be towards
   the top.

IV. FUTURE VERSIONS OF PM FingerD

12/05/95  PM FIngerD v1.0c:
             Fixed a couple of identifaction bugs.
             It reported everyone as being logged on.
             This is wrong.  It is fixed now.

12/02/95  PM FingerD v1.0b:
             Added user configuration dialog box and
             .PLN file support, still needs timeout
             support worked on.

11/28/95  PM FingerD v1.0a:
             First release, very light version.

   -------------------

   I will continue to update this daemon, as I hunger for more features.
   I am planning to add customization features on the details of the
   incoming fingers, as well as loggin these to a file.  Other properties
   and configuration options for the daemon will be nice later on too.

   I'll get to writing a .INF file for the currently disabled HELP buttons,
   but for now, there is nothing too complex that can't be intuitively
   figured out from this server to require a HELP file.

   If you have any suggestions on what to add next to this simple but
   cool finger service, just drop me an e-mail.
   Or if you have any bug reports and such, send them too.

V. DISCLAIMER
   This program is freeware.
   You may use and copy this program as you see fit, though I will not
   be liable for any damages this program may do to your hardware or
   software (data or executables)

--------------------------------
                                       Amilcar M. Ubiera
                                       amubiera@eos.ncsu.edu
                                       Junior in Computer Science at NCSU
                                       http://www.catt.ncsu.edu/~leo
