# IBM_PROLOG_BEGIN_TAG 
# This is an automatically generated prolog. 
#  
#  
#  
# Licensed Materials - Property of IBM 
#  
# (C) COPYRIGHT International Business Machines Corp. 2014,2021 
# All Rights Reserved 
#  
# US Government Users Restricted Rights - Use, duplication or 
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 
#  
# IBM_PROLOG_END_TAG 
#
# sccsid = "@(#)60   1.10   src/rsct/utils/ctfile.cfg, common_utils, rsct_rady, radys004a 8/11/21 08:19:27"
#
# PURPOSE:
# The ctfile.cfg file controls the tracing and logging of various RSCT components. 
#
# DESCRIPTION: 
# To initiate tracing and logging control, system administrators can create the RSCT file configuration (RFC) file, /etc/ctfile.cfg. A system administrator can copy a
# sample configuration file, /opt/rsct/cfg/ctfile.cfg, to the /etc directory, and then modify it. The control information in the configuration file takes 
# effect the next time a specified component, a daemon, for example, is started.
# The RSCT components that support tracing and logging control, which are listed in the sample configuration file, 
# obtain the following configuration information from the /etc/ctfile.cfg file. 
#   (I)  An absolute path to a directory tree under which the component's trace files and log files are to be written. This path can refer to a remote file system.
#   (II) A flag that indicates whether tracing is to be disabled for each component.
#   (III)When tracing is enabled, the size of a trace file for each component and each trace file. Some components write to several trace files.
#   (IV) The amount of information to be traced.
#   (V)  A flag that indicates whether logging is to be disabled for each component.
#   (VI) A flag that indicates whether logging is to be disabled for all RSCT components.
#
# Below is the format of the control information contained in this file
#
# CT_TRACE_LOG_ROOT_DIR=<path_name_prefix>    ( Prefix must start with '/'. The default root directory is /var/ct. )
# CT_TRACE_DISABLE={true|false}  [<component_name>]
# CT_TRACE_FILE_SIZE=nnn[k]  <component_name>  <file_name>  ( nnn is the size of the specified trace file in bytes. 
#                                                             If the optional K suffix is specified, the size is specified in 
#                                                             units of 1024 bytes.)
# CT_TRACE_LEVELS=<category_level_sting>  <component_name>
# CT_LOGGING_DISABLE={true|false}  [<component_name>]
# CT_ROOT_USER_TMP_DIRECTORY=<path_name>
# CT_NON_ROOT_USER_TMP_DIRECTORY=<path_name>
# CT_DMS_TIMEOUT=<time in secs>[s]                         ( The value has to be >=15 secs )
#                                                            Specifying 's' is optional. )
# CritDaemonRestartGracePeriod=<time in secs>[s]
# CT_CRASHDUMP_ON_PANIC={false}               ( This is to disable system panic with kernel dump
#                                               as part of critical resource protection. )
# CT_SIMULATE_REMOTE_NODE_DOWN_PERIOD=<time in secs>[s]
#
#
#
# Remove "#" and update the entry to be effective
#
#CT_TRACE_LOG_ROOT_DIR=/var/ct
#CT_TRACE_DISABLE=
#CT_TRACE_FILE_SIZE=
#CT_TRACE_LEVELS=
#CT_LOGGING_DISABLE=
#CT_ROOT_USER_TMP_DIRECTORY=
#CT_NON_ROOT_USER_TMP_DIRECTORY=
#CT_DMS_TIMEOUT=15
#CritDaemonRestartGracePeriod=
#CT_CRASHDUMP_ON_PANIC=
#CT_SIMULATE_REMOTE_NODE_DOWN_PERIOD=