Creating Namespace Contexts Under NIS+

When your primary enterprise-level name service is NIS+, namespace contexts must be created separately for each NIS+ domain or subdomain in your enterprise.

• The NIS+ domain or subdomain must already be in existence.

• If you intend to use the same server for both NIS+ and FNS, the fncreate command must be run on the domain's (or subdomain's) master server. If you intend to use different servers for NIS+ and FNS, the fncreate command must be run on the machine that will function as the FNS server. (If you are going to use different machines, the FNS server must first be prepared as explained in Step 4.)

• You must have full NIS+ administration authorization (see Solaris Naming Administration Guide for information on NIS+ authorization).

For example, to create the contexts for the manf.doc.com subdomain on the submaster machine which is the NIS+ master server for that domain:

1. On the subdomain master, run fncreate as shown below:

submaster# fncreate -t org org/manf.doc.com./

This creates the organization context for the NIS+ manf.doc.com. subdomain, and contexts and associated subcontexts for all users found in that subdomain's passwd.org_dir table and all hosts found in the subdomain's hosts.org_dir table.

(If you want to use different machines for NIS+ and FNS servers, you would run the above command on the machine you want to use as the FNS server. See Step 4 for information on how to prepare a non-NIS+ server to be an FNS server.)

1. Use nisping to checkpoint the ctx_dir directory:

   # /usr/lib/nis/nisping -C ctx_dir.manf.doc.com.

   ---

   Note -

   For a large organization with several thousand users and hosts, the initial fncreate operation can take several hours; the subsequent checkpoint can also take several hours.

   ---