ypxfr(1M)                                               ypxfr(1M)



NAME
     ypxfr - transfers a Network Information Service (NIS) map to
     the local system

SYNOPSIS
     ypxfr [-c] [-d domain-name] [-f] [-h host-name] map-name

     ypxfr -d domain-name [-C tid prog ipadd port] map-name

ARGUMENTS
     -c   Causes ypxfr not to send a ``Clear map'' request to the
          local ypserv process. You should use this option if
          ypserv is not running on the local system at the time
          you invoke ypxfr.  Otherwise, ypxfr displays an error
          message stating that it can't talk to the local ypserv,
          and the transfer fails.

     -C tid prog ipadd port
          Causes ypxfr to call back a yppush process from the
          host with the Internet address specified by ipadd,
          registered as the program specified by prog, listening
          on port specified by port, and waiting for a response
          to the transaction specified by tid.  This option is
          used only when ypserv starts up ypxfr.

     -d domain-name
          Causes ypxfr to use the domain specified by domain-name
          rather than the local system's domain.

     -f   Forces the transfer to occur even if the version on the
          master server is not more recent than the local
          version.

     -h host-name
          Gets the map from the system specified by host-name,
          regardless of what the map says about the master
          server.  If you do not use this option, ypxfr gets the
          map from the master server.  The value of host-name can
          be a host name or an Internet address. If you do not
          use this option or if the value of host-name is a host
          name, ypxfr uses NIS to determine the Internet address
          of the system from which to get the map.

     map-name
          Specifies the name of the map to transfer.

DESCRIPTION
     ypxfr transfers an NIS map to the local system by using NIS
     services.  It creates a temporary map in the directory
     /etc/yp/domainname, fills it by enumerating the map's
     entries, and fetches and loads the map master and order
     number.  It then deletes the old versions of the map and



January 1992                                                    1

ypxfr(1M)                                               ypxfr(1M)



     moves the temporary map to the real map name.

     If ypxfr is run interactively, it writes its output to the
     terminal. However, if it is invoked without a controlling
     terminal and if the log file /etc/yp/ypxfr.log exists, ypxfr
     appends all its output to that file.  Because ypxfr is most
     often started by cron or by ypserv, you can use the log file
     to retain a record of what was attempted and the results.

     To maintain consistency between servers, you should run
     ypxfr periodically for every map in the NIS database.
     Different maps change at different rates:  The
     services.byname map may not change for months at a time and
     may be checked only once a day at a time when the system is
     not busy.  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 updates.  You can use a crontab entry to
     perform periodic updates automatically.

     Rather than having a separate crontab entry for each map,
     you can group commands to update several maps in a shell
     script.  These sample shell scripts are in /etc/yp:
     ypxfr_1d.sh, ypxfr_2d.sh, and ypxfr_1h.sh.

     Refer to ypfiles(4) and ypserv(1M) for an overview of NIS.

FILES
     /etc/yp/ypxfr
          Executable file
     /etc/yp/ypxfr.log
          File in which ypxfr records its actions
     /etc/yp/ypxfr_1d.sh
          Script file that queries the master server once per day
     /etc/yp/ypxfr_2d.sh
          Script file that queries the master server twice per
          day
     /etc/yp/ypxfr_1h.sh
          Script file that queries the master server once per
          hour

SEE ALSO
     yppush(1M), ypserv(1M)

     ypfiles(4) in A/UX Programmer's Reference

     Chapter 4, ``Setting Up the Network Information Service,''
     in A/UX Network System Administration








2                                                    January 1992