Planning and Configuring HP-UX DCE 1.9

Chapter 6
Configuring HP-UX DCE Cells
Configuring Cells Using dce_config
62
Additional Notes About Log Messages
ERROR messages—if dce_config is being run using a here-document (dce_config<< input_file) or when
using dce_config -e config.env -c config.cmd, the environment variable EXIT_ON_ERROR should be
set to y and exported to prevent errors from causing the here-document to get out of sync with dce_config.
(Also, CHECK_TIME should be set to n and exported when running dce_config from a here-document.) See
the ksh (1) manpage for more information about here-documents.
VERBOSE messages containing "User query:" or "User entry:" contain a complete record of user entries in
executing dce_config. The top of the log files contains a set of VERBOSE messages showing the settings of
environment variables. These can all be used to reproduce a user's execution of dce_config.
Only ERROR: or WARNING: messages indicate actual occurrence of a problem.
Component Scripts and Environment Variables for dce_config
This section contains information useful for those who want to run dce_config from custom scripts. This
section includes a description of the special-purpose component scripts that are called by dce_config, as well
as a list and description of the environment variables that allow you to supply configuration input to
dce_config.
dce_config Component Scripts
In a custom configuration script, you may want to directly call the following dce_config component scripts.
Unless otherwise noted, these scripts reside in /opt/dce/bin or /etc/opt/dce:
• dce_shutdown: Kills running HP-UX DCE daemons. Cannot be run remotely; must be run on affected
DCE client or server node. Should be run before reconfiguring DCE.
• dce.rm: Removes data and configuration files created by DCE daemons after initial configuration. Should
be run before reconfiguring DCE. Cannot be run remotely; must be run on affected DCE client or server
node.
• dce.unconfig hostname : Removes DCE client on hostname from the Security and Directory service
databases. Should be run before reconfiguring DCE on a client system.
VERBOSE V:<message> Low-level summary of actions being taken,
user queries and responses, or actual
commands executed that do not affect
configuration or node state. Logged to log
file unless LOG_THRESHOLD is DETAIL or
higher. Not logged to display unless
DISPLAY_THRESHOLD is VERBOSE or lower.
DEBUG DEBUG:<message> Actual commands executed that show only
where in the dce_config script the actions
are taking place. Also used for recording
sleep commands. Frequently contain error
message text, since error text is passed to
script functions for display if an error
occurs. Do not confuse these message with
actual error occurrences.
Table 6-1 dce_config Message Categories (Continued)
Priority Format Content