*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->Linux man pages -> yppush (8)              



NAME    [Toc]    [Back]

       yppush - force propagation of changed NIS databases

SYNOPSIS    [Toc]    [Back]

       /usr/sbin/yppush [ -d domain ] [ -t timeout ] [ -p # parrallel jobs ] [
       -h host ] [ -v ] mapname ...

DESCRIPTION    [Toc]    [Back]

       yppush copies updated NIS databases  (or  maps)	from  the  master  NIS
       server  to  the	slave  servers within a NIS domain. It is normally run
       only on the NIS master by /var/yp/Makefile after the  master  databases
       are  changed.   /var/yp/Makefile does not invoke yppush by default, the
       NOPUSH="True" line must be commented out.
       yppush first constructs a list of NIS slave servers by reading the  NIS
       map  ypservers  within  the  domain.   A destination host (or a list of
       hosts with multiple -h commands) can also be specified on  the  command
       line.   A  "transfer  map"  request  is	sent to the NIS serger at each
       slave, along with the information needed by the transfer agent ypxfr(8)
       to  callback to yppush, which may be printed the result to stderr. Messages
 are also pritned when a transfer  isnot  possible;  for  instance
       when the request message is undeliverable.

OPTSIONS    [Toc]    [Back]

       -d domain
	      Specify  a  particular  domain. The NIS domain of the local host
	      system is used by default. If the local host's  domain  name  is
	      not set, the domain name must be specified with this flag.

       -t timeout
	      The  timeout flag is used to specify a timeout value in seconds.
	      This timeout controls how long yppush will wait for  a  response
	      from a slave server before sending a map transfer request to the
	      next slave server in the list.  By default, yppush will wait  90
	      seconds. For big maps, this is not long enough.

       -p # parallel jobs
	      yppush  normally	performs  transfers  serially, meaning that it
	      will send a map transfer request to one slave  server  and  then
	      wait  for  it  to  respond  before sending the next map transfer
	      request to the next slave  server.  In  environments  with  many
	      slaves,  it  is more efficient to initiate several map transfers
	      at once so that the transfers can take place in parallel.

       -h host
	      The host flag can be used to transfer a map to a	user-specified
	      machine or group of machines instead of the list of servers contained
 in the ypservers map. A list of hosts can be specified by
	      using  multiple  instances  of  the  -h  flag.  -v Verbose mode:
	      causes yppush to print debugging messages as it runs. Note specifying
 this flag twice makes yppush even more verbose.

SEE ALSO    [Toc]    [Back]

       domainname(1), ypserv(8), ypxfr(8)

BUGS    [Toc]    [Back]

       The  mechanism  for  transferring  NIS maps in NIS v1 is different that
       that in NIS version 2. This version of  has  support  for  transferring
       maps to NIS v2 systems only.

AUTHOR    [Toc]    [Back]

       Thorsten Kukuk <kukuk@suse.de>

NYS YP Server			  August 1996			     YPPUSH(8)
[ Back ]
 Similar pages
Name OS Title
yppush IRIX force propagation of a changed NIS map
yppush Tru64 force propagation of a changed Network Information Service (NIS) map
yppush FreeBSD force propagation of updated NIS databases
yppush HP-UX force propagation of Network Information Service database
class_database_modified Tru64 determines if the database has changed
DtWsmAddWorkspaceModifiedCallback HP-UX add a callback to be called when any workspace is changed
udetect Tru64 Find subset files that have changed since installation
yppush OpenBSD force distribution of YP map
DtActionCallbackProc HP-UX notify application that the status of an application has changed
streampipes HP-UX force all pipes to be STREAMS-based
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service