Installation guide

Class Code Operational Events
350 Diagnostic status messages
351 Repair and maintenance messages
You can specify the following severity levels:
Severity Level Description
* All severity levels
severe
Unrecoverable events that are usually fatal to system operation
high
Recoverable events or unrecoverable events that are not fatal to
system operation
low
Informational events
You can specify the following destinations:
Destination Description
Full pathname Specifies the file name to which the binlogd daemon appends
the binary event records.
@
hostname Specifies the name of the host (preceded by an @) to which the
binlogd daemon forwards the binary event records. If you
specify dumpfile for an event class, you cannot forward records
to a host.
13.2.2 Creating the Special Files
The syslogd daemon cannot log kernel messages unless the /dev/klog
character special file exists. If the /dev/klog file does not exist, create it
by using the following command syntax:
/dev/MAKEDEV /dev/klog
Also, the binlogd daemon cannot log local system events unless the
/dev/kbinlog character special file exists. If the /dev/kbinlog file does
not exist, create it by using the following command syntax:
/dev/MAKEDEV /dev/kbinlog
Refer to the MAKEDEV
(8) reference page for more information.
13.2.3 Starting and Stopping Event-Logging Daemons
The syslogd and binlogd daemons are automatically started by the init
program during system startup. However, you must ensure that the
Administering Events and Errors 13–9