OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
The multiple files are named by appending a dot to the simple specified
name, followed by the current generation number. When the number of
entries in a file reaches the maximum specified by count, the file is
closed, the generation number is incremented, and the next file is
opened. When the maximum generation number 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, as long as messages are being
written. 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.
dest (destination) Specifies where the message should be sent, and is a
pathname. The field can be left blank if the out_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 colons, semicolons, or periods.
Multiple routings for the same severity level can be specified by simply adding the
additional desired routings as semicolon-separated strings in the following format:
out_form:dest
For example, consider the following:
FATAL:TEXTFILE:/dev/console
WARNING:DISCARD:--
NOTICE:BINFILE.50.100:/tmp/log%ld;STDERR:-
These strings specify that
• Fatal error messages should be sent to the console.
• Warnings should be discarded.
• Notices should be written both to standard error and as binary entries in files located
in the /tmp directory. No more than 50 files should be written, and there should be
no more than 100 messages written to each file. The files will have names of the form
/tmp/logprocess_id.nn
where process_id is the process ID of the program originating the messages, and nn
is the generation number of the file.
The GOESTO specifier allows messages for the severity whose routing specification it
appears in to be routed to the same destination (and in the same output form) as those for
the other, specified, severity level (or component name). For example, the following
specification:
WARNING:STDERR:;GOESTO:FATAL
FATAL:STDERR:;FILE:/tmp/foo
4− 24 Tandem Computers Incorporated 124245