Initializes a workstation to be a NIS+ client.
nisinit [ -c [ -k key_domain ] [ -C coldstart | -H host| -B ]]
nisinit -r
[ -p Y| D| N parent_domain_host... ]
The nisinit command initializes a workstation to be an NIS+ client. 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.
- -Ccoldstart
- Causes the file coldstart to be used as a prototype coldstart file when initializing a NIS+ client. This coldstart file can be copied from a machine that is already a client of the NIS+ namespace. For maximum security, an administrator can encrypt and encode (with uuencode(1C)) the coldstart file and mail it to an administrator bringing up a new machine. The new administrator would then decode (with uudecode), decrypt, and then use this file with the nisinit command to initialize the machine as an NIS+ client. If the coldstart file is from another client in the same domain, the nisinit command may be safely skipped and the file copied into the /var/nis directory as /var/nis/NIS_COLD_START.
- -Hhostname
- Specifies that the host hostname should be contacted as a trusted NIS+ server. The nisinit command will iterate over each transport in the NETPATH environment variable and attempt to contact rpcbind on that machine. This hostname must be reachable from the client without the name service running. For IP networks this means that there must be an entry in /etc/hosts for this host when nisinit is invoked.
- -B
- Specifies that the nisinit command should use an IP broadcast to locate a NIS+ server on the local subnet. Any machine that is running the NIS+ service may answer. No guarantees are made that the server that answers is a server of the organization's namespace. If this flag is used, it is advisable to check with your system administrator that the server and domain served are valid. The binding information can be written to the standard output using the nisshowcache command.
Note: nisinit -c will just enable navigation of the NIS+ namespace from this client. To make NIS+ your name service, modify the file /etc/nsswitch.conf to reflect that.
- Y
- Specifies that the parent directory is a NIS version 2 domain.
- D
- Specifies that the parent directory is a DNS domain.
- N parent_domain_host...
- Specifies that the parent directory is another NIS+ domain. This flag is useful for connecting a pre-existing NIS+ subtree into the global namespace.
nisinit -c -B nisinit -c -H hostname nisinit -c -C filename
nisinit -r
Initializing a Client
Note: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 nsswitch.conf file must have files as the first choice on the hosts line. Complete instructions for each method, including prerequisites and associated tasks, are provided in Initializing an NIS+ Client . Following is a summary of the steps that use the nisinit command.
nisinit -c -H hostname
nisinit -c -C filename
nisinit -c -B
Initializing the Root Master Server
nisinit -r
/var/nis/NIS_COLD_START | This file contains a list of servers, their transport addresses, and their Secure RPC public keys that serve the machine's default domain. |
/var/nis/data/root.object | This file describes the root object of the NIS+ namespace. It is standard XDR-encoded NIS+ directory object that can be modified by authorized clients using the nis_modify() interface. |
/var/nis/data/parent.object | This file describes the namespace that is logically above the NIS+ namespace. The most common type of parent object is a DNS object. This object contains contact information for a server of that domain. |
/etc/hosts | Internet host table. |
The nisclient command, and nisshowcache command.