OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components
generation number is incremented, and the next file is
opened.
When the maximum number of files have been created and
filled, the generation number is reset to 1, and a new file
with that number is created and written to (thus overwriting
the already-existing file with the same name), and so on.
Thus the files wrap around to their beginning, and the total
number of log files never exceeds gens, although messages
continue to be written as long as the program continues
writing them.
destination Specifies where the message should be sent, and is a
pathname. You can leave this field blank if the output_form
specified is DISCARD, STDOUT,or STDERR. The field
can also contain a %ld string in the filename which, when
the file is written, will be replaced by the process ID of the
program that wrote the message(s). Filenames may not
contain : (colon), ; (semicolons), % (percent sign), or the
space character.
application-defined Is used for application-specific information. Standard DCE
programs ignore it.
9.4.2.1.1 String Syntax
The string syntax for a serviceability routing specification is
severity:output_form:destination[: application-defined][; . . . ]
Note that you can define multiple routing specifications as a semi-colon separated list.
For example, this specification
FATAL:TEXTFILE:/dev/console;STDOUT:
ERROR:TEXTFILE.5.100:/tmp/errors
EXIT:DISCARD:
*:FILE:/tmp/svc-log
NOTICE:BINFILE:/tmp/log%ld
WARNING:STDOUT:
instructs the serviceability mechanism to do the following:
• Send fatal error messages to the console and to standard output
• Send other error messages to a log-rolled file
• Discard normal exit reports
• Write all messages to a log file
• Send informational messages to a temporary binary log
9− 12 Tandem Computers Incorporated 124243