FNS Administration Privileges

FNS System administration varies according to the underlying naming service:

• NIS+. Under NIS+, FNS system administration tasks can only be performed by those with authorization to do so. The usual method of granting system administration privileges is to create an NIS+ group and assign that group the necessary privileges for that domain. Any member of the group can then perform system administration functions.

• NIS. Under NIS, FNS administration tasks must be performed by root on the NIS master server.

• Files. Under a files-based naming system, FNS administration tasks must be performed by someone with root access to the /var/fn directory.

The ability of users to make changes to their own user sub-contexts varies according to the underlying naming service:

• NIS+. Under NIS+, a user's context (and associated sub-contexts) are owned by them. When logged in as an NIS+ principle, users who have the appropriate credentials and privileges can make changes to their own context using the fncreate, fnbind, fnunbind, and similar commands.

• NIS. Under NIS, users cannot make any changes to any FNS data. Only those with root access on the NIS master server can change FNS data.

• Files. Under a files-based naming system, users own their own contexts. Standard UNIX access controls apply to FNS files.