Information Technology Reference
In-Depth Information
The NFS server logging consists of two phases. The first phase is performed
by the
kernel
; it records RPC requests in a work buffer. The second phase is
performed by the
daemon
; it reads the work buffer and constructs the log
records. The amount of time the daemon waits before reading the work
buffer along with other configurable parameters are specified in the
/etc/default/nfslogd
file.
Because NFS uses file handles instead of pathnames, a database that maps these
file handles to pathnames is maintained as part of the logging operation.
The /etc/default/nfslogd File
The following configuration parameters, as defined in the
/etc/default/
nfslogd
file, affect the behavior of the NFS logging daemon. The initial
nfslogd
provided with the Solaris 9 system contains only comments.
CYCLE_FREQUENCY
—Amount of time (in hours) of the log cycle (close cur-
rent log and open new one). This is to prevent the logs from getting too
large.
➤
IDLE_TIME
—Amount of time (in seconds) that the logging daemon will
sleep while waiting for data to be placed in the work buffer.
➤
MAPPING_UPDATE_INTERVAL
—The amount of time (in seconds) between
updates of the file handle to pathname mapping database.
➤
MAX_LOGS_PRESERVE
—The maximum number of log files to save.
➤
MIN_PROCESSING_SIZE
—Minimum size (in bytes) of the work buffer
before the logging daemon will process its contents.
➤
PRUNE_TIMEOUT
—The amount of time (in hours) the access time of a file
associated with a record in the pathname mapping database can remain
unchanged before it is removed.
➤
UMASK
—
umask
used for the work buffer and file handle to pathname
mapping database.
➤
The /etc/nfs/nfslog.conf File
The
/etc/nfs/nfslog.conf
file is used to specify the location of log files,
file handle to pathname mapping database, and work buffer, along with a
few other parameters. Because a set of parameters are grouped together
and are associated with a tag or name, multiple instances of configurations
