xref: /titanic_44/usr/src/man/man1m/yppush.1m (revision a60349c89adffc0902b2353230891d8e7f2b24d9)
te
Copyright (c) 2000, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
YPPUSH 1M "Aug 26, 1999"
NAME
yppush - force propagation of changed NIS map
SYNOPSIS

/usr/lib/netsvc/yp/yppush [-v] [-h host] [-d domain]
 [-p #parallel-xfrs] mapname
DESCRIPTION

yppush copies a new version of a Network Information Service (NIS) map from the master NIS server to the slave NIS servers. It is normally run only on the master NIS server by the Makefile in /var/yp after the master databases are changed. It first constructs a list of NIS server hosts by reading the NIS ypservers map within the domain. Keys within the ypservers map are the ASCII names of the machines on which the NIS servers run.

A "transfer map" request is sent to the NIS server at each host, along with the information needed by the transfer agent (the program that 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 can 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 the NIS service.

OPTIONS

The following options are supported: -d domain

Specifies a domain.

-h host

Propagates only to the named host.

-p #parallel-xfrs

Allows the specified number of map transfers to occur in parallel.

-v

Verbose. This prints messages when each server is called, and for each response. If this flag is omitted, only error messages are printed.

FILES
/var/yp

Directory where NIS configuration files reside.

/var/yp/domain/ypservers.\|{dir, pag\|}

Map containing list of NIS servers to bind to when running in server mode.

SEE ALSO

ypserv(1M), ypxfr(1M), ypfiles(4), attributes(5)

NOTES

The Network Information Service (NIS) was formerly known as Sun Yellow Pages (YP). The functionality of the two remains the same; only the name has changed. The name Yellow Pages is a registered trademark in the United Kingdom of British Telecommunications PLC, and must not be used without permission.

BUGS

In the current implementation (version 2 NIS protocol), the transfer agent is ypxfr(1M), 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.