Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Naming and Directory Services (NIS+) |
Part I About Naming and Directory Services
Part II NIS+ Setup and Configuration
4. Configuring NIS+ With Scripts
5. Setting Up the NIS+ Root Domain
8. Configuring an NIS+ Non-Root Domain
10. NIS+ Tables and Information
12. Administering NIS+ Credentials
14. Administering Enhanced NIS+ Security Credentials
15. Administering NIS+ Access Rights
16. Administering NIS+ Passwords
18. Administering NIS+ Directories
Using the niscat Command With NIS+ Directories
Listing the Object Properties of an NIS+ Directory
Using the nisls Command With Directories
Listing the Contents of an NIS+ Directory - Terse
Listing the Contents of an NIS+ Directory - Verbose
Adding an NIS+ Replica to an Existing Directory
Disassociating a Replica From an NIS+ Directory
Removing NIS+ Nondirectory Objects
Changing rpc.nisd Syntax Options
Starting and Stopping the NIS+ Cache Manager
Displaying the Contents of the NIS+ Cache
Pinging and Checkpointing in NIS+
Displaying When NIS+ Replicas Were Last Updated
Checkpointing an NIS+ Directory
Displaying the Contents of the NIS+ Transaction Log
Changing the Time-to-Live of an NIS+ Object
Changing the Time-to-Live of an NIS+ Table Entry
20. NIS+ Server Use Customization
23. Information in NIS+ Tables
Common NIS+ Namespace Error Messages
This section describes how to initialize a machine client using the nisinit command. An easier way to do this is with the nisclient script as described in Setting Up NIS+ Client Machines.
The nisinit command initializes a machine to be an NIS+ client or server. As with the rpc.nisd command, you don't need any access rights to use the nisinit command, but you should be aware of its prerequisites and related tasks. These are described in Initializing an NIS+ Client.
You can initialize a client in three different ways:
By host name
By broadcast
By cold-start file
Each way has different prerequisites and associated tasks. For instance, before you can initialize a client by host name, the client's /etc/hosts file must list the host name you will use and the nsswitch.conf file must have files as the first choice on the hosts line.
Note - Prior to the Solaris 10 7/07 release, before you can initialize an IPv6 client by host name, the client's /etc/inet/ipnodes file must list the host name you will use. For IPv6 addresses, specify ipnodes as the first choice on the hosts line of the nsswitch.conf file.
Following is a summary of the steps that use the nisinit command.
To initialize a client by host name, use the -c and -H options, and include the name of the server from which the client will obtain its cold-start file:
nisinit -c -H hostname
To initialize a client by cold-start file, use the -c and -C options, and provide the name of the cold-start file:
nisinit -c -C filename
To initialize a client by broadcast, use the -c and -B options:
nisinit -c -B
To initialize the root master server, use the nisinit -rcommand:
nisinit -r
You will need the following information
The superuser password of the machine that will become the root master server.
The name of the new root domain. The root domain name must have at least two elements (labels) and end in a dot (for example, something.com.). The last element must be either an Internet organizational name (as shown in Table 18-4), or a two or three character geographic identifier such as .jp. for Japan.
Table 18-4 Internet Organizational Domains
|