ypxfr(1M)                                               ypxfr(1M)



     NAME
          ypxfr - transfer a YP map from some YP server to here

     SYNOPSIS
          ypxfr [-f] [-h host] [-d domain] [-c] [-C tid prot ipadd
          port] mapname

     DESCRIPTION
          ypxfr moves a YP map to the local host by making use of nor-
          mal YP services.  It creates a temporary map in the directo-
          ry /etc/yp/domainname (which must already exist), fills it
          by enumerating the map's entries, fetches the map parameters
          (master and order number) and loads them.  It then deletes
          any old versions of the map and moves the temporary map to
          the real mapname.

          If ypxfr is run interactively, it writes its output to the
          terminal.  However, if it's invoked without a controlling
          terminal, and if the log file /etc/yp/ypxfr.log exists, it
          will append all its output to that file.  Since ypxfr is
          most often run from cron(1M), or by ypserv, you can use the
          log file to retain a record of what was attempted, and what
          the results were.

          For consistency between servers, ypxfr should be run period-
          ically for every map in the YP data base.  Different maps
          change at different rates:  the services.byname map may not
          change for months at a time, for instance, and may therefore
          be checked only once a day in the wee hours.  You may know
          that mail.aliases or hosts.byname changes several times per
          day.  In such a case, you may want to check hourly for up-
          dates.  A crontab(1) entry can be used to perform periodic
          updates automatically.  Rather than having a separate cron-
          tab entry for each map, you can group commands to update
          several maps in a shell script.  Examples (mnemonically
          named) are in /etc/yp:  ypxfr_1d.sh, ypxfr_2d.sh, and
          ypxfr_1h.sh.  They can serve as reasonable first cuts.

          Refer to ypfiles(4) and ypserv(1M) for an overview of the
          yellow pages.

     FLAG OPTIONS
          -f        Force the transfer to occur even if the version at
                    the master is not more recent than the local ver-
                    sion.

          -c        Don't send a ``Clear map'' request to the local
                    ypserv process.  Use this flag if ypserv is not
                    running locally at the time you are running ypxfr.
                    Otherwise, ypxfr will complain that it can't talk
                    to the local ypserv, and the transfer will fail.




     April, 1990                                                     1

     ypxfr(1M)                                               ypxfr(1M)



          -h host   Get the map from host, regardless of what the map
                    says the master is.  If host is not specified,
                    ypxfr will ask the YP service for the name of the
                    master and try to get the map from there.  host
                    may be a name or an internet address in the form
                    ww.xx.yy.zz.

          -d domain Specify a domain other than the default domain.

          -C tid prog ipadd port
                    This option is only for use by ypserv.  When yp-
                    serv invokes ypxfr, it specifies that ypxfr should
                    call back a yppush process at the host with IP ad-
                    dress ipaddr, registered as protocol prot, listen-
                    ing on port port, and waiting for a response to
                    transaction tid.

     FILES
          /etc/ypxfr
          /etc/yp/ypxfr.log
          /etc/yp/ypxfr_1d.sh
          /etc/yp/ypxfr_2d.sh
          /etc/yp/ypxfr_1h.sh

     SEE ALSO
          ypserv(1M), yppush(1M), ypfiles(4),
          A/UX Network Applications Programming.




























     2                                                     April, 1990