HP Visualize J210XC IRIX to HP-UX Migration Guide - Page 88

etc/hosts, SLAVE1# /USR/ETC/NSD -A NIS_SECURITY=LOCAL, ypset, ypwhich, ypinit

Page 88 highlights

NIS 1. If the slave is not on the same network as cats, verify that the master server has an entry in /etc/hosts on the slave server: slave1# grep circles /etc/hosts 192.0.2.4 cats.bigdogs.com cats 2. Whether or not the slave is on the same network as cats, you should halt any existing nsd, and start the binding process with the specified attribute of nsd: SLAVE1# /USR/ETC/NSD -A NIS_SECURITY=LOCAL 3. Give the ypset command to point nsd at the server cats. Then verify that the server is bound by giving the ypwhich command. slave1# ypset cats slave1# ypwhich cats Building the Duplicate Maps By transferring a copy of the original maps from the NIS master server to the slave, ypinit builds the duplicate database maps. Follow these steps: 1. Determine which system is the master server with the ypwhich command. 2. Start building NIS slave server maps with the ypinit command. The -s flag specifies that this system is to be an NIS slave server, and cats is the master server: slave1# cd /var/yp slave1# ./ypinit -s circles Each line of the ypinit output contains the name of a map and the name of the master server where the map was created: Transferring map networks.byname from server cats.bigdogs. Transferring map services.byname from server cats.bigdogs. Transferring map passwd.byname from server cats.bigdogs. Transferring map hosts.byaddr from server cats.bigdogs. Transferring map ktools from server cats.bigdogs. Transferring map ypservers from server cats.bigdogs. Transferring map hosts.byname from server cats.bigdogs. Transferring map networks.byaddr from server cats.bigdogs. Transferring map protocols.byname from server cats.bigdogs. Transferring map group.byname from server cats.bigdogs. Transferring map netgroup from server cats.bigdogs. Transferring map mail.aliases from server cats.bigdogs. Transferring map ethers.byname from server cats.bigdogs. Transferring map protocols.bynumber from server cats.bigdogs. Transferring map netgroup.byhost from server cats.bigdogs. Transferring map group.bygid from server cats.bigdogs. Transferring map passwd.byuid from server cats.bigdogs. Transferring map ethers.byaddr from server cats.bigdogs. Transferring map netgroup.byuser from server cats.bigdogs. Starting NIS on the Slave Server The NIS service is available to clients as soon as you start it on this slave server. 83

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125

NIS
83
1.
If the slave is not on the same network as
cats
, verify that the master server has an entry in
/etc/hosts
on
the slave server:
slave1# grep circles /etc/hosts
192.0.2.4
cats.bigdogs.com cats
2.
Whether or not the slave is on the same network as
cats
, you should halt any existing
nsd
, and start the
binding process with the specified attribute of
nsd
:
SLAVE1# /USR/ETC/NSD -A NIS_SECURITY=LOCAL
3.
Give the
ypset
command to point
nsd
at the server
cats
. Then verify that the server is bound by giving
the
ypwhich
command.
slave1# ypset cats
slave1# ypwhich
cats
Building the Duplicate Maps
By transferring a copy of the original maps from the NIS master server to the slave,
ypinit
builds the
duplicate database maps.
Follow these steps:
1.
Determine which system is the master server with the
ypwhich
command.
2.
Start building NIS slave server maps with the
ypinit
command. The
–s
flag specifies that this system is
to be an NIS slave server, and
cats
is the master server:
slave1# cd /var/yp
slave1# ./ypinit -s circles
Each line of the
ypinit
output contains the name of a map and the name of the master server where the
map was created:
Transferring map networks.byname from server cats.bigdogs.
Transferring map services.byname from server cats.bigdogs.
Transferring map passwd.byname from server cats.bigdogs.
Transferring map hosts.byaddr from server cats.bigdogs.
Transferring map ktools from server cats.bigdogs.
Transferring map ypservers from server cats.bigdogs.
Transferring map hosts.byname from server cats.bigdogs.
Transferring map networks.byaddr from server cats.bigdogs.
Transferring map protocols.byname from server cats.bigdogs.
Transferring map group.byname from server cats.bigdogs.
Transferring map netgroup from server cats.bigdogs.
Transferring map mail.aliases from server cats.bigdogs.
Transferring map ethers.byname from server cats.bigdogs.
Transferring map protocols.bynumber from server cats.bigdogs.
Transferring map netgroup.byhost from server cats.bigdogs.
Transferring map group.bygid from server cats.bigdogs.
Transferring map passwd.byuid from server cats.bigdogs.
Transferring map ethers.byaddr from server cats.bigdogs.
Transferring map netgroup.byuser from server cats.bigdogs.
Starting NIS on the Slave Server
The NIS service is available to clients as soon as you start it on this slave server.