ypinit(1M) ypinit(1M)
NAME
ypinit - set up masters and slaves
SYNOPSIS
cd /var/yp; ypinit -c Format 1
cd /var/yp; ypinit -m Format 2
cd /var/yp; ypinit -s mastername Format 3
DESCRIPTION
This command is used to
- define a host as a client computer
- define a master server and install the NIS database on it (For-
mat 2)
- define a slave server and copy the NIS files to it (Format 3).
In addition to the master, slaves should also be defined in the net-
work. The slaves can relieve the master of part of its workload if the
system is heavily loaded. Defining a slave also increases the security
of the data in the NIS files.
The ypinit command generates the NIS files on the master in the
/var/yp/domain directory (domain is the name of the domain that the
master manages.)
The NIS files are generated either
- from information available to the command at runtime
or
- from the standard ASCII files.
The following are the standard ASCII files:
/etc/yppasswd global user names
/etc/ypgroup global user groups
/etc/rpc RPC services
/etc/ethers assignment of Ethernet address to Internet
address
/etc/inet/hosts accessible hosts
/etc/inet/networks defined networks
Page 1 Reliant UNIX 5.44 Printed 11/98
ypinit(1M) ypinit(1M)
/etc/inet/services all the services in the network
/etc/inet/protocols protocol types
/etc/inet/timed permissible masters and slaves for synchroni-
zation
/var/yp/mail.aliases global mailing list
/var/yp/ypservers NIS servers
/var/yp/netgroup network groups
/var/yp/autoupdaters auto-update clients
When setting up a master, the ypinit command assumes that the host at
which the command is issued manages all the standard NIS files. If the
command is used to define a slave, the NIS files are copied from the
master specified to the host at which the command is issued.
Regardless of whether you set up a network administration host, proxy
host or client - ypinit will always first terminate any NIS daemons
that may be active. Once the setup is complete, all necessary daemons
are restarted.
Format 1
-c Identifies the machine on which the command was issued as a NIS
client with no particular privileges. The NIS files are retained
on the NIS master and its slaves.
The ypbind and yptransd daemons are started, as well as the
ypxfrserv(1M) daemon for auto-update clients.
Format 2
-m defines the host at which the command is issued as the master
server. At the same time, the standard NIS files are generated in
the /var/yp/domain directory. domain is the name of the domain
that is managed by the master.
The command functions interactively and expects certain input
(see example). The future slaves must be specified, for example.
The ypbind, ypserv, ypupdated and in.yppasswdd daemons are
started on the network administration host.
Page 2 Reliant UNIX 5.44 Printed 11/98
ypinit(1M) ypinit(1M)
Format 3
-s defines the host at which the command is issued as a slave
server.
mastername
is the name of the master from which the NIS files are to be
copied.
The ypbind and ypserv daemons are started on the proxy host.
EXAMPLES
Example 1
The saturn host is set up as the network administration host for the
planets domain.
Questions on updating the local /etc/passwd and /etc/group files
relate to how the network administration host behaves as its own
client. The various procedures and associated commands and files are
explained in the manual "Networking Administrator's Guide".
# ypinit -m
Preparing the environment...
Installing saturn in domain planets as a yp master.
Killing all currently active NIS daemons...Done.
Please choose how to take over global user and group entries.
Enter the number of the selected item (RETURN selects item 1).
1) New Style (using /etc/passwd.local and /etc/group.local)
2) Old SINIX style (using /var/yp/pwpattern)
3) Restricted old SINIX style (only user/group names and IDs are updated)
4) No global users and groups
> 1
Setting GLOBALPW to "new".
In order for YP to operate successfully, we have to construct a list of the
YP servers. Please continue to add the names for YP servers in order of
preference, one per line.
When you are done with the list, type a <control D>.
next host to add: saturn
next host to add: uranus
next host to add: <^D>
The current list of yp servers looks like this:
saturn
uranus
Is this correct? [y/n: y] <CR>
Installing the YP database will require that you answer a few questions.
Page 3 Reliant UNIX 5.44 Printed 11/98
ypinit(1M) ypinit(1M)
Questions will all be asked at the beginning of the procedure.
Do you want this procedure to quit on non-fatal errors? [y/n: n] <CR>
OK, please remember to go back and redo manually whatever fails. If you
don't, some part of the system (perhaps the yp itself) won't work.
The yp domain directory is /var/yp/planets
There will be no further questions. The remainder of the procedure
should take a few minutes.
Running /var/yp/Makefile
updated ypservers
>>/etc/yppasswd
updated passwd
>>/etc/ypgroup
updated group
updated hosts
updated networks
>>/var/yp/netgroup
updated netgroup
updated protocols
updated services
updated rpc
>>/var/yp/mail.aliases
updated mail
>>/etc/inet/timed
updated timed
updated autoupdaters
If there are active slave yp servers, run yppush now for any databases
which have been changed. If there are no active slaves, run ypinit on
those hosts which are to be slave servers.
saturn has been set up as a yp master server without any errors.
Starting NIS daemons...Done.
Example 2
The uranus host is set up as a proxy host for the saturn network
administration host in the planets domain.
Questions on updating the local /etc/passwd and /etc/group files
relate to how the proxy host behaves as its own client. The various
procedures and associated commands and files are explained in the
manual "Networking Administrator's Guide".
# ypinit -s saturn
Preparing the environment...
Installing uranus in domain planets as a yp server.
Page 4 Reliant UNIX 5.44 Printed 11/98
ypinit(1M) ypinit(1M)
Killing all currently active NIS daemons...Done.
Please choose how to take over global user and group entries.
Enter the number of the selected item (RETURN selects item 1).
1) New Style (using /etc/passwd.local and /etc/group.local)
2) Old SINIX style (using /var/yp/pwpattern)
3) Restricted old SINIX style (only user/group names and IDs are updated)
4) No global users and groups
> 1
Setting GLOBALPW to "new".
Installing the YP database will require that you answer a few questions.
Questions will all be asked at the beginning of the procedure.
Do you want this procedure to quit on non-fatal errors? [y/n: n] <CR>
OK, please remember to go back and redo manually whatever fails. If you
don't, some part of the system (perhaps the yp itself) won't work.
The yp domain directory is /var/yp/planets
Can we destroy the existing /var/yp/planets and its contents? [y/n: n] y
There will be no further questions. The remainder of the procedure should take
a few minutes, to copy the databases from uranus.
Transferring mail.aliases...
Transferring rpc.byname...
Transferring rpc.bynumber...
Transferring services.byname...
Transferring timed...
Transferring autoupdaters...
Transferring services.byport...
Transferring protocols.byname...
Transferring netgroup.byhost...
Transferring netgroup.byuser...
Transferring netgroup...
Transferring networks.byaddr...
Transferring networks.byname...
Transferring hosts.byaddr...
Transferring hosts.byname...
Transferring group.bygid...
Transferring group.byname...
Transferring passwd.byuid...
Transferring passwd.byname...
Transferring protocols.bynumber...
Transferring ypservers...
uranus' yellow pages database has been set up without any errors.
Starting NIS daemons...Done.
Page 5 Reliant UNIX 5.44 Printed 11/98
ypinit(1M) ypinit(1M)
Example 3
The neptun host is set up as an auto-update client in the planets
domain.
Questions on updating the local /etc/passwd and /etc/group files
relate to the required procedure for incorporating global user and
group entries into the local files. The various procedures and associ-
ated commands and files are explained in the manual "Networking
Administrator's Guide".
# ypinit -c
Preparing the environment...
Installing neptun in domain planets as a yp client.
Killing all currently active NIS daemons...Done.
Please choose how to take over global user and group entries.
Enter the number of the selected item (RETURN selects item 1).
1) New Style (using /etc/passwd.local and /etc/group.local)
2) Old SINIX style (using /var/yp/pwpattern)
3) Restricted old SINIX style (only user/group names and IDs are updated)
4) No global users and groups
> 1
Setting GLOBALPW to "new".
In order for YP to operate successfully, we have to construct a list of the
YP servers. Please continue to add the names for YP servers in order of
preference, one per line.
When you are done with the list, type a <control D>.
next host to add: saturn
next host to add: uranus
next host to add: <^D>
The current list of yp servers looks like this:
saturn
uranus
Is this correct? [y/n: y] <CR>
Do you wish to enable automatic local ascii file updates on
this client when new maps are pushed out to the slaves? [y/n: n] y
Starting ypxfrserv...
NOTE: To receive automatic updates you must also add this
host to the list of ypservers on the master.
Updating the client's data files...
Installation as a yp client completed.
Page 6 Reliant UNIX 5.44 Printed 11/98
ypinit(1M) ypinit(1M)
Since the client is to be set up as an auto-update client, it must be
identified as such on the saturn network administration host in the
/var/yp/autoupdaters file:
# echo neptun >> /var/yp/autoupdaters
# cd /var/yp
# make autoupdaters
SEE ALSO
makedbm(1M), map2system(1M), ypmake(1M), yppush(1M), ypserv(1M),
ypxfr(1M), ypxfrserv(1M), autoupdaters(4), ypfiles(4), ypservers(4).
Page 7 Reliant UNIX 5.44 Printed 11/98