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

  man pages->IRIX man pages -> yppush (1)              
Title
Content
Arch
Section
 

Contents


yppush(1M)							    yppush(1M)


NAME    [Toc]    [Back]

     yppush - force propagation	of a changed NIS map

SYNOPSIS    [Toc]    [Back]

     yppush [ -d domain	] [ -v ] mapname

DESCRIPTION    [Toc]    [Back]

     yppush copies a new version of the	specified NIS map from the master NIS
     server to the slave NIS servers.  It is normally run only on the master
     server by ypmake(1M) after	the master databases are changed.  It first
     constructs	a list of NIS server hosts by reading the ypservers map	within
     the domain.  Keys within the ypservers map	are the	hostnames of the
     domain's NIS servers.

     A ``transfer map''	request	is sent	to the NIS server at each host,	along
     with the information needed by the	transfer agent (the program which
     actually moves the	map) to	call back the yppush.  When the	attempt	has
     completed (successfully or	not), and the transfer agent has sent yppush a
     status message, the results may be	printed	to stdout.  Messages are also
     printed when a transfer is	not possible; for instance when	the request
     message is	undeliverable, or when the timeout period on responses has
     expired.

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

OPTIONS    [Toc]    [Back]

     -d	domain	 Specify a domain.

     -v		 Verbose.  This	causes messages	to be printed when each	server
		 is called, and	for each response.  If this flag is omitted,
		 only error messages are printed.

FILES    [Toc]    [Back]

     /var/ns/domain/domain/ypservers.m

SEE ALSO    [Toc]    [Back]

      
      
     ypserv(1M), ypxfr(1M), ypfiles(4).

BUGS    [Toc]    [Back]

     In	the current implementation (version 2 NIS protocol), the transfer
     agent is ypxfr, which is started by the ypserv program.  If yppush
     detects that it is	speaking to a version 1	NIS protocol server, it	uses
     the older protocol, sending a version 1 YPPROC_GET	request	and issues a
     message to	that effect.  Unfortunately, there is no way of	knowing	if or
     when the map transfer is performed	for version 1 servers.	yppush prints
     a message saying that an "old-style" message has been sent.  The system
     administrator should later	check to see that the transfer has actually
     taken place.


									PPPPaaaaggggeeee 1111
[ Back ]
 Similar pages
Name OS Title
yppush Linux force propagation of changed NIS databases
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
gzforce IRIX force a '.gz' extension on all gzip files
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service