Manual page for nisinit(1M)
nisinit - NIS+ client and server initialization utility
initializes a machine to be a
client or an
root master server.
It may be easier to use
to accomplish this same task.
Initialize the machine to be a
This option creates the file
and initialize it to contain information about this machine.
It uses the
system call to retrieve the name of the default domain.
To initialize the machine as an NIS+ root server, it is advisable to use the
instead of using ``nisinit -r''.
- -p Y | D | N parent_domain host ...
This option is used on a root server to initialize a
to make this domain a part of the namespace above it.
Only root servers can have parent objects.
A parent object describes the namespace ``above'' the
If this is an isolated domain, this option should not be used.
The argument to this option tells the command what type of name server is
serving the domain above the
domain. When clients attempt to resolve a name that is outside of the
namespace, this object is returned with the error
indicating that a name space boundary has been reached. It is up to the
client to continue the name resolution process.
is the name of the parent domain in a syntax that is native to that type
of domain. The list of host names that follow the domain parameter
are the names of hosts that serve the parent domain. If there is more than
one server for a parent domain, the first host specified should be the
master server for that domain.
Specifies that the parent directory is a NIS version 2
Specifies that the parent directory is a DNS
Specifies that the parent directory is another
domain. This option is useful for connecting a pre-existing
subtree into the global namespace.
Note that in the current implementation, the
clients do not take advantage of the
feature. Also, since the parent object is currently not replicated on root replica servers,
it is recommended that this option not be used.
Initializes the machine to be a
There are three initialization options available: initialize
by coldstart, initialize by hostname, and initialize by broadcast.
The most secure mechanism is to initialize from a trusted coldstart file.
The second option is to initialize using a hostname that you specify
as a trusted host.
The third method is to initialize by broadcast and it is the
least secure method.
- -C coldstart
Causes the file coldstart to be used as a prototype
coldstart file when initializing a
This coldstart file can be copied from a machine that is already
a client of the
For maximum security, an administrator can encrypt and encode (with
the coldstart file and mail it to an administrator bringing up a new machine.
The new administrator would then decode (with
decrypt, and then use this file
with the nisinit command to initialize the machine as an
If the coldstart file is from another client in the same domain,
the nisinit command may be safely skipped and the file copied
- -H hostname
Specifies that the host hostname should be contacted as
The nisinit command will iterate over each transport
environment variable and attempt to contact
on that machine.
This hostname must be reachable from the
client without the name service running.
networks this means
that there must be an entry in
for this host when
nisinit is invoked.
Specifies that the nisinit command should use an IP
broadcast to locate a
server on the local subnet.
Any machine that is running the
service may answer.
No guarantees are made that the server that answers is a server of the
If this option is used, it is advisable to check with your
system administrator that the server and
domain served are valid. The binding
information can be dumped to the standard output using the
will just enable navigation of the
name space from this client. To make
your name service, modify the file
to reflect that. See
for more details.
returns 0 on success and 1 on failure.
This example initializes the machine as an
client using the host
as a trusted server.
example# nisinit -cH freddy
This example sets up a client using a trusted coldstart file.
example# nisinit -cC /tmp/colddata
This example sets up a client using an IP broadcast.
example# nisinit -cB
This example sets up a root server.
example# nisinit -r
This environment variable may be set to the transports to try when
The client library will only attempt to contact the server using
connection oriented transports.
This file contains a list of servers, their transport addresses, and their
Secure RPC public keys that serve the machine's default domain.
This file describes the root object of the
namespace. It is a standard XDR-encoded
directory object that can be modified by authorized clients using the
This file describes the namespace that is logically above the
namespace. The most common type of parent object is a DNS object.
This object contains contact information for a server of that domain.
Internet host table.
Created by unroff & hp-tools.
© by Hans-Peter Bischof. All Rights Reserved (1997).
Last modified 21/April/97