OSF DCE Administration Guide--Core Components

Managing DCE Host Services and Host Data
• Send warnings to standard output
9.4.2.1.2 Tcl Syntax
The Tcl syntax for a serviceability routing specification is
{severity output_form destination application-defined}
where severity, output_form, destination, and application-defined are specified as
previously described. In Tcl syntax, multiple routing specifications take the following
form:
{{specification}{specification}{specification}}
For example, the sample specification shown previously for string format would be
expressed in Tcl syntax as follows:
{FATAL { {TEXTFILE /dev/console} STDOUT} }
{ERROR TEXTFILE.5.100 /tmp/errors}
{EXIT DISCARD}
{* FILE /tmp/svc-log}
{NOTICE BINFILE /tmp/log%ld }
{WARNING STDOUT {} }
9.4.2.2 Using a Routing File
If a file called dce-local-path/var/svc/routing exists, the contents of the file (if in the
proper format) will be used to determine the routing of messages written by the
serviceability mechanism.
The default location of the serviceability routing file is normally
/opt/dcelocal/var/svc/routing. However, you can specify a different location for the file
by setting the value of the environment variable DCE_SVC_ROUTING_FILE to the
complete desired pathname.
The routing file contains lines that specify the routing desired for the various kinds of
messages (based on message severity level). Each line consists of three fields as follows:
severity:output_form:destination[: application-defined][; . . . ]
You can supply multiple routings by specifying additional output_form:destination pairs
as a semicolon-separated list.
In the routing file, blank lines beginning with the # character are treated as comments.
124243 Tandem Computers Incorporated 9− 13