Related Informatio n
Section 9.5: Managing Local Logging on page 301.
5.1.1. Log Daemon Specific Configuration
This window controls configuration of the log daemon and the central HPSS log.
Field Descriptions
Log File Maximum Size. The maximum size in bytes of each central log file. The default value is
5,242,880 (5 MB). Once the maximum size is reached, logging will switch to a second log file. The log
file that filled up will then be archived to an HPSS file if the Archive Flag is on. Since two log files are
allocated to accommodate log switching and log file archiving, the amount of space used by logging will
be twice the specified value.
Switch Logfiles. A flag that indicates whether a switch to the second log file should be performed if the
archive of the second log file has not yet completed. Use the default value of Always. Although a log
may not get archived, the alternative may be a loss of logged messages to the current log from running
servers.
Daemon Port. The port number for communication between the Log Client and the Log Daemon. The
default value is 8100. Ensure that the port number assigned does not conflict with a ny other application
on the node. The port value must be a different value than the Client Port number in the Log Client
configuration entries.
Archive Logfiles. A flag that indicates whether log files should be archived when they fill.
Archive Class of Service. When a log file exceeds Log File Maximum Size, it will be archived to this
class of service if the Archive Logfiles flag is set.
Log Directory. The name of the UNIX directory in which log files are stored. The default value is
/var/hpss/log.
5.1.2. Migration/Purge Se rver (MPS) Specific Conf iguration
This tab of the Migration Purge Server Configuration window allows you to upda te/view the type-
specific configuration parameters for a Migration/Purge Server (MPS).
As with any other part of the server configuration, updates made here are written directl y to metadata
with no involvement by the server. The server, if already running, must be recycled in order for the
changes to become effective.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 101