OSF DCE Administration Guide--Introduction

OSF DCE Administration Guide—Introduction
Debug messages have the form:
DEBUG: message text
Some sample debug messages follow:
DEBUG: Executing: daemon_slayer(dtsd)
DEBUG: dtsd can’t be killed, not running
6.3.7 The dce_config log File
In addition to being displayed on the screen, messages are also written to the dce_config
log file, /tmp/dce_config.log. As with the screen displays, you can control the type of
messages logged in the file using the environment variables described in Chapter 10. By
default the log file is named dce_config.log and resides in the tmp directory. You can
specify a different name and location with the LOGFILE environment variable
described in Chapter 10.
A portion of a sample log file is shown in Figure 6-1.
Note that the sample is in four basic sections:
• The first section displays the name of the machine being configured (indicated by
host_name)
• The second section displays the dce_config version number (indicated by
version_num) and time and date dce_config was run. (indicated by date_and_time)
• The third section shows the settings of the environment variables described in
Chapter 10.
• The final section shows a portion of the actual messages produced during a machine
configuration
dce_config logfile for host host_name
*****************************************************************
dce_config V: version_num executed: date_and_time
*****************************************************************
V: EXIT_ON_ERROR: n
V: DO_CHECKS: y
V: REMOVE_PREV_INSTALL: <not set>
V: REMOVE_PREV_CONFIG: <not set>
V: SEC_SERVER: <not set>
V: SEC_SERVER_IP: <not set>
V: UNCONFIG_HOST_PRESET: <not set>
V: CELL_NAME: <not set>
V: KEYSEED: <not set>
V: CACHE_CDS_SERVER: <not set>
V: CACHE_CDS_SERVER_IP: <not set>
V: REP_CLEARINGHOUSE: <not set>
V: HOSTNAME_IP: <not set>
6− 6 Tandem Computers Incorporated 124244