ypinit(1m) - osol9

1ypinit(1M)              System Administration Commands              ypinit(1M)
2
3
4

NAME

6       ypinit - set up NIS client
7

SYNOPSIS

9       /usr/sbin/ypinit [-c] [-m] [-s master_server]
10
11

DESCRIPTION

13       ypinit  can  be  used  to  set up an NIS client system. You must be the
14       superuser to run this command. This script need not be used at  all  if
15       ypbind(1M)  is  started  with the -broadcast option (it is invoked with
16       this option from the svc:/network/nis/client:default service).
17
18
19       Normally, ypinit is run only once after installing the system.  It  may
20       be run whenever a new NIS server is added to the network or an existing
21       one is decommissioned.
22
23
24       ypinit prompts for a list of NIS servers to bind the  client  to;  this
25       list  should  be ordered from the closest to the furthest server. It is
26       recommended that you list each of these NIS servers by name and numeric
27       IP  address  in /etc/hosts. Though the practice is not recommended, NIS
28       allows  you  to  list  servers  by  numeric  address  only,   bypassing
29       /etc/hosts.  In  such  a  configuration,  ypwhich(1)  returns a numeric
30       address instead of a name.
31
32
33       ypinit stores the list of servers to which a client  can  bind  in  the
34       file /var/yp/binding/domain/ypservers. This file is used by ypbind when
35       run without the -broadcast option.
36

OPTIONS

38       -c
39
40           Set up a ypclient system.
41
42
43       -m
44
45           Build a master ypserver data base.
46
47
48       -s master_server
49
50           Slave data base. master_server must be the same  master  configured
51           in the YP maps and returned by the ypwhich -m command.
52
53

FILES

55       /etc/hosts
56
57           File in which it is recommended that NIS servers be listed.
58
59
60       /var/yp/binding/domain/ypservers
61
62           Lists the servers to which the NIS client is allowed to bind.
63
64

ATTRIBUTES

66       See attributes(5) for descriptions of the following attributes:
67
68
69
70
71       ┌─────────────────────────────┬─────────────────────────────┐
72       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
73       ├─────────────────────────────┼─────────────────────────────┤
74       │Availability                 │SUNWnisu                     │
75       └─────────────────────────────┴─────────────────────────────┘
76

NOTES

82       The NIS client service is managed by the service  management  facility,
83       smf(5), under the service identifier:
84
85         svc:/network/nis/client:default
86
87
88
89
90       Administrative actions on this service, such as enabling, disabling, or
91       requesting restart, can be performed using  svcadm(1M).  The  service's
92       status can be queried using the svcs(1) command.
93

BUGS

95       ypinit  sets  up the list of NIS servers only for the current domain on
96       the system when it  is  run,  that  is,  the  domain  returned  by  the
97       SI_SRPC_DOMAIN  command  to  sysinfo(2). Care should be taken to ensure
98       that this is the same as the desired domain for NIS client processes.
99
100
101
102SunOS 5.11                        20 Dec 2007                       ypinit(1M)