Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   20652 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

ypinit(1M)		System Administration Commands		    ypinit(1M)

NAME
       ypinit - set up NIS client

SYNOPSIS
       /usr/sbin/ypinit [-c] [-m] [-s master_server]

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. Each of
       these NIS servers must be listed in the /etc/hosts file along with  its
       IP   address.   ypinit	stores	 the   list   in   file	 /var/yp/bind‐
       ing/domain/ypservers. This file is used by ypbind when run without  the
       -broadcast option.

OPTIONS
       -c		   Set up a ypclient system.

       -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

       /var/yp/binding/domain/ypservers

ATTRIBUTES
       See attributes(5) for descriptions of the following attributes:

       ┌─────────────────────────────┬─────────────────────────────┐
       │      ATTRIBUTE TYPE	     │	    ATTRIBUTE VALUE	   │
       ├─────────────────────────────┼─────────────────────────────┤
       │Availability		     │SUNWnisu			   │
       └─────────────────────────────┴─────────────────────────────┘

SEE ALSO
       svcs(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.

SunOS 5.10			  17 Aug 2006			    ypinit(1M)

Vote for polarhome