ypxfr(1M)																 ypxfr(1M)

NAME

       ypxfr, ypxfr_1perday, ypxfr_1perhour, ypxfr_2perday - transfer NIS database from server to local node

SYNOPSIS

       domain] host] domain]
	      tid prog server] mapname

   Remarks
       The  Network  Information  Service  (NIS) was formerly known as Yellow Pages (YP).  Although the name has changed, the functionality of the
       service remains the same.

DESCRIPTION

       copies a Network Information Service (NIS) map (database) to the local host from a NIS server by using the NIS  services.   A  map  can	be
       copied regardless of its age, or it can be copied depending on whether its modification time (order number) is more recent than that of the
       local map.

       The command creates a temporary map in directory where domain is the NIS domain.  The command fills the map with mapname  entries,  obtains
       the map parameters (master and order number), and loads them.  It then clears the old version of mapname and moves the temporary map to the
       existing mapname.

       If is run interactively, it writes messages to standard output.	If is invoked without a controlling terminal and if the log  file  exists,
       appends	all  its  messages  to that file.  Since is usually run from the superuser's file (see crontab(1)) or by (see yppush(1M)), the log
       file can retain a record of what attempted and what the results were.

       To maintain consistency between NIS servers, should be executed periodically for every map in the NIS database.	Different maps	change	at
       different  rates.   For	example,  the map may not change for months at a time, and might therefore be checked for changes only once a day,
       such as in the early morning hours.  However, may change several times per day, so hourly checks for updates might be more appropriate.

       A file can perform these periodic checks and transfers automatically.  Rather than having a separate file for each  map,  requests  can	be
       grouped	in  a shell script to update several maps at once.  Example scripts (mnemonically named) are in and They serve as reasonable rough
       drafts that can be changed as appropriate.

       Refer to ypfiles(4) and ypserv(1M) for an overview of the Network Information Service.

   Options
       recognizes the following options:

	      Preserve the resolver flag in the map during transfer.

	      Do not send a "clear current map" request to the local
			     process.  Use this flag if is not running locally when you are running Otherwise, complains that it  cannot  talk	to
			     the local and the transfer fails.	If is running locally, do not use this flag.

	      Copy the map from a NIS server in
			     domain rather than the domain returned by (see domainname(1)).

	      Force the map to be copied, even if its order number at the remote NIS
			     server is not more recent than the order number of the local map.

	      Obtain the map from
			     host,  regardless	of its master server.  If this option is not used, asks the NIS service for the master's host name
			     and tries to obtain its map.  The host can be a name or an IP address of the form

	      Specify a source domain from which to transfer a map that should be
			     the same across domains (such as the map.

	      When	     invokes it specifies that should call back a process (that initiated the transfer) at the host server, registered	as
			     program number prog, and waiting for a response to transaction tid.

AUTHOR

       was developed by Sun Microsystems, Inc.

FILES

       Log file

       The following scripts are suggested for use with

       Run one transfer per day

       Run two transfers per day

       Hourly transfers of "volatile" maps

SEE ALSO

       crontab(1), domainname(1), cron(1M), ypinit(1M), yppush(1M), ypserv(1M), ypfiles(4).

																	 ypxfr(1M)