Establishing Secure RPC domains

For many networked systems, a single Secure RPC domain will suffice. Administrators are notified of the domain name, and they use the domainname(1Mnis) command to establish that name as the Secure RPC domain name for their machine. For example, to set the a machine's domain name to research:

domainname research

For networked systems having multiple domains, the process is the same, except that two or more different domains will be in use in the network.

Administrators should also set their machine's SRPC_DOMAIN tunable to their Secure RPC domain name, as described in ``Setting the Secure RPC domain name''. If this is not done, the domain name will be forgotten across reboots.

A machine can be part of only one domain at any given time. The decision to use single or multiple domains depends on need. In general, the advantages of multiple domains include:

• Duplicate operating system/user ID pairs can be using Secure RPC (provided they are in different domains).

• Access to Secure RPC programs can be made selective, if some programs are not available to all domains.