Manual page for nisfiles(4)
nisfiles - NIS+ database files and directory structure
The Network Information Service Plus (NIS+)
uses a memory based, replicated database.
This database uses a set of files in the
directory for checkpointing to stable storage and for maintaining a
server and client use files in this directory to store binding
and state information.
service implements an authentication and authorization system that is
built upon Secure RPC.
In this implementation, the service uses a table named
to store the public and private keys of principals that are authorized
to access the
It stores group access information in the subdomain
These two tables appear as files in the
directory on the
Unlike the previous versions of the network information service in
the information in the tables
is initially loaded into the service from the
files on the server and then updated using
Some sites may wish to periodically regenerate the
files for archival purposes.
To do this, a script should be added in the
of the server
that lists these tables and creates the
file from the result.
Note: Except for the
no other files should be manipulated by commands such as
The transaction log file keeps logs of all changes made, and
hence the files cannot be manipulated independently.
The files described below are stored in the
This file contains
directory objects that are to be preloaded into the
cache at startup time.
This file is usually created at
This file contains the current cache of
bindings being maintained by the cache manager.
The contents can be viewed with
This file contains a transaction log that is maintained by the
It can be viewed using the
This file contains holes.
Its apparent size may be a lot higher than its actual size.
There is only one transaction log per server.
This file is a dictionary that is used by the
database to locate
It is created by the default
This is the log file for the database dictionary.
When the server is checkpointed (nisping -C),
this file will be deleted.
This directory contains databases that the server uses.
On root servers, this file contains a directory object that
describes the root of the name space.
On root servers, this file contains a directory object that describes
the parent namespace.
This file is created by the
For each table in the directory there will be a file with the same name
that stores the information about that table.
If there are subdirectories within this directory,
the database for the table is stored in the file
This file contains the database log for the table
The log file maintains the state of individual transactions to each
When a database has been checkpointed
(that is, all changes have been made to the
this log file will be deleted.
does not automatically do checkpointing.
The system administrator may want to do
operations periodically (such as, once a day)
to checkpoint the log file.
This can be done either through a
job, or manually.
On root servers, this file stores the database associated with the root
It is similar to other table databases.
The corresponding log file is called
This table contains the credentials of principals in this
This table contains the group authorization objects needed by
to authorize group access.
This file contains a list of all NIS+ directories that are being served
by the NIS+ server on this server. When this server is added or deleted
from any NIS+ directory object, this file is updated by the server.
Created by unroff & hp-tools.
© by Hans-Peter Bischof. All Rights Reserved (1997).
Last modified 21/April/97