xref: /titanic_50/usr/src/man/man1m/ypinit.1m (revision 37915d862fc5cc87b5b702954d7d7f16a9f98e5c)
te
Copyright 1989 AT&T
Copyright (C) 2008, 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]
Copyright 2014 Nexenta Systems, Inc. All rights reserved.
YPINIT 1M "Dec 15, 2014"
NAME
ypinit - set up NIS client
SYNOPSIS

/usr/sbin/ypinit -m
/usr/sbin/ypinit -s [master_server]
/usr/sbin/ypinit -c [server_name...]
DESCRIPTION

ypinit can be used to set up an NIS client system. You must be the superuser to run this command. This script need not be used at all if ypbind(1M) is started with the -broadcast option (it is invoked with this option from the svc:/network/nis/client:default service).

Normally, ypinit is run only once after installing the system. It may be run whenever a new NIS server is added to the network or an existing one is decommissioned.

ypinit prompts for a list of NIS servers to bind the client to; this list should be ordered from the closest to the furthest server. It is recommended that you list each of these NIS servers by name and numeric IP address in /etc/hosts. Though the practice is not recommended, NIS allows you to list servers by numeric address only, bypassing /etc/hosts. In such a configuration, ypwhich(1) returns a numeric address instead of a name.

ypinit stores the list of servers to which a client can bind in the file /var/yp/binding/domain/ypservers. This file is used by ypbind when run without the -broadcast option.

OPTIONS
-c [server_name...]

Set up a ypclient system. If server_name is specified, it will replace currently configured list of servers. server_name could be represented by IPv4/v6 address as well as by hostname.

-m

Build a master ypserver data base.

-s master_server

Slave data base. master_server must be the same master configured in the YP maps and returned by the ypwhich -m command.

FILES
/etc/hosts

File in which it is recommended that NIS servers be listed.

/var/yp/binding/domain/ypservers

Lists the servers to which the NIS client is allowed to bind.

SEE ALSO

svcs(1), ypwhich(1), svcadm(1M), ypbind(1M), sysinfo(2), hosts(4), attributes(5), smf(5)

NOTES

The NIS client service is managed by the service management facility, smf(5), under the service identifier:

svc:/network/nis/client:default

Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The service's status can be queried using the svcs(1) command.

BUGS

ypinit sets up the list of NIS servers only for the current domain on the system when it is run, that is, the domain returned by the SI_SRPC_DOMAIN command to sysinfo(2). Care should be taken to ensure that this is the same as the desired domain for NIS client processes.