An FNS (XFN) term referring to a special atomic name used to refer to the root of a namespace.
In FNS (XFN), a connected set of contexts of the same type (having the same naming convention) and providing the same set of operations with identical semantics. In the UNIX operating environment, for example, the set of directories in a given file system (and the naming operations on directories) constitutes a naming system.
A number used by software to separate the local subnet address from the rest of a given Internet protocol address.
In FNS (XFN), a reference to a context in which composite names from subordinate naming systems are resolved.
See Secure RPC password.
A distributed network information service containing key information about the systems and the users on the network. The NIS database is stored on the master server and all the replica or slave servers.
A file used by NIS that holds information of a particular type, for example, the password entries of all users on a network or the names of all host machines on a network. Programs that are part of the NIS service query these maps. See also NIS.
A distributed network information service containing hierarchical information about the systems and the users on the network. The NIS+ database is stored on the master server and all the replica servers.
A configuration of NIS+ that allows NIS clients to have access to the data stored in NIS+ tables. When in this mode, NIS+ servers can answer requests for information from both NIS and NIS+ clients.
For administrative purposes, an NIS+ environment refers to any situation in which the applicable nsswitch.conf file points to nisplus. Or any time a command is run with an option that forces it to operate on objects in an NIS+ namespace (for example, passwd -r nisplus).
An NIS+ domain, directory, table, or group. See domain, directory, group, and table.
See principal.
A file that contains data updates destined for the NIS+ tables about objects in the namespace. Changes in the namespace are stored in the transaction log until they are propagated to replicas. The transaction log is cleared only after all of a master server's replicas have been updated.
See next naming system pointer.
In FNS (XFN), an enterprise is organized into organizational units such as centers, laboratories, departments, divisions, and so on. An organizational unit is a subunit of an enterprise.
In FNS (XFN), a context for naming objects related to an organizational unit within an enterprise.
In FNS (XFN), a context in which this context and its siblings are bound.
See domain.
The process by which an NIS+ master server transfers a change a NIS+ data to the domain's replica servers.
A number which a machine uses to rank the order in which it tries to obtain namespace information from NIS+ servers. A machine will first try all servers with a given rank number before trying any server with the next highest rank number. For example, a machine will query NIS+ servers with a rank number of 0 before it queries any server with a rank number of 1.
From the point of view of a client machine, a preferred NIS+ server is a server that the client should try to use for namespace information ahead of non-preferred servers. Servers that are listed in a client or domain's preferred server list are considered preferred servers for that client or domain.
A client_info table or a client_info file. Preferred server lists specify the preferred servers for a client or domain.
Any user of NIS+ information whose credentials have been stored in the namespace. Any user or machine that can generate a request to a NIS+ server. There are two kinds of NIS+ principal: client users and client machines:
Root principal. A machine root user (user ID = 0). Requires only a DES credential.
User principal. Any nonroot user (user ID > 0). Requires local and DES credentials.