ppagesd(1M)

NAME
     ppagesd -  PeoplePages database server

SYNOPSIS
     /usr/etc/ppagesd [-t ttl ] dirpath bookname

DESCRIPTION
     ppagesd is the dynamic networked peoplepages(1) database server.  It has
     two functions: it provides the location of the NFS-mountable PeoplePages
     database directory to peoplepages, and it listens for entry data from
     InPersonTM and stores the received data into the database.  The
     peoplepages application uses NFS and the automount(1M) to access the
     database.

     ppagesd is started at system initialization if the configuration flag
     ppagesd is set ``on'' with chkconfig(1M).  The 2 required site-dependent
     arguments to ppagesd belong in the file /etc/config/ppagesd.options.

     The dirpath argument is the absolute pathname of a directory to hold the
     database files.  The bookname argument specifies a "logical" name for the
     database.  It also determines which entry data packets should be
     examined.  To store entries from InPerson users, it should be "InPerson".

     To start ppagesd servers for several books, put the dirpath/bookname
     pairs on separate lines in the ppagesd.options file.

     For each bookname, only one machine on a local area network should be
     configured as the server.

     The optional ttl argument specifies the time-to-live for the multicast
     packets sent out in answer to queries from PeoplePages clients.  This is
     the maximum number of gateways through which the packets will be
     forwarded.

DETAILS
     When peoplepages starts up, it sends out a query to find the location of
     PeoplePages databases.  ppagesd replies with the bookname and dirpath
     information: the directory name is prepended with "/hosts/<hostname>" so
     that the PeoplePages can use automount(1M) to access the directory via
     NFS.  ppagesd also listens for multicast packets from inperson(1) and
     stores them in the database if no entry exists.

     Each entry in the database is a file containing name:value pairs. Each
     line can be up to 1024 characters including the trailing nul character.

     If you create an entry for a user in the public database, and you want to
     allow them to modify it later, be sure to use chown(1M) to change the
     file ownership to the user.  If you don't want them to modify, then don't
     change the ownership.
CUSTOMIZING THE DATABASE
     You can customize both the name and the cover of your book as shown on
     the book-selection button at the top of peoplepages's main window.  The
     name goes into the file .label in the database directory.  Two cover
     images in either .xpm (X Pixmap) or .rgb (standard SGI) format are
     required.  One is displayed when the book is closed, the other when it is
     opened for reading.  They go in the files .cover-closed and .cover-open
     in the database directory.  The images should be 44 by 32 pixels.  Xpm
     format is recommended because it allows you to tag the predominant
     background color of the pixmap.  Having this information allows InPages
     to do make a better visual presentation of your images.  To tag the
     background add " s background" at the end of the line specifying the
     predominant background color.  For example the line

           % c #848484

     becomes

           % c #848484 s background


EXAMPLES
     To store InPerson entries in /var/ppages/inperson,
     /etc/config/ppagesd.options should contain

          /var/ppages/inperson InPerson


     To start servers for InPerson entries as well a list of conference room
     entries, put the following lines in ppagesd.options:

          /var/ppages/inperson InPerson
          /var/ppages/conf     Conference


FILES
     /etc/config/ppagesd.options

SEE ALSO
     peoplepages(1), inperson(1)
     PeoplePages Administrator's Guide

NOTE
     The NFS optional software must be installed and configured to export the
     specified database directory(s).  Write access to the directory(s) is
     needed if users are permitted to change their entries using
     peoplepages(1).  Use the chmod(1) command to change the permissions and
     set the sticky bit restrict the right to delete records to the owner of
     the record:
          chmod 1777 directory


     If users are on different networks, the network administrator should
     configure multicast routers between the networks for ppagesd to receive
     location requests and entry data from users.  See mrouted(1M) and the
     InPerson Setup and Admin Guide for details.