binlogd - Binary event-log daemon
/usr/sbin/binlogd [-d] [-f config_file]
Enables debugging. Specifies the alternate binary configuration file.
The binlogd daemon logs binary event records to the files specified in the /etc/binlog.conf configuration file. You must use a formatting tool to read the error log files and a number of options are identified later in this reference page. In a future release, uerf will be retired and replaced by Compaq Analyze.
Each binary event record includes an event class and priority code, which are described in /usr/sys/include/dec/binlog/*.h. The binlogd reads from the /bin/kbinlog special device and from the Internet domain socket specified in the /etc/services file. The binlogd daemon is configured when it starts up and when it receives a hangup signal.
The /etc/binlog.conf file contains entries that specify the event class, the severity level, and the destination to which the binlogd daemon sends the messages. Each line of the /etc/binlog.conf file contains an entry.
The event class and the severity level are separated by a period (.). The event class and severity level are separated from the destination by one or more tabs. Blank lines and lines beginning with a # (number sign) are ignored.
If you specify an asterisk (*) for an event class or severity level, all event classes or all severity levels are selected. The event class is specified as a decimal number. The available class codes are specified in /usr/sys/include/dec/binlogd.h and are as follows:
CPU machine checks and exceptions Memory Disks Tapes Device controllers Adapters Buses Stray interrupts Console events Stack dumps SCSI CAM events
CI port-to-port driver events System communications services events
Generic ASCII informational messages
ASCII startup messages ASCII shutdown messages Panic messages Timestamp Diagnostic status messages Repair and maintenance messages
You can specify the following severity levels: Specifies events that cannot be recovered and that are usually fatal to system operation. Specifies events that either can be recovered or cannot be recovered but are not fatal to system operation. Specifies informational messages.
The destination for the messages can be either the full pathname of a local file or the name of a remote system. The remote host must be known to the system. You specify a remote system as follows:
You can specify dumpfile instead of an event class and severity level to identify the pathname of the file that will contain the kernel binary event-log buffer, which the savecore command recovers from a system dump.
The default /etc/binlog.conf file causes the binlogd daemon to create a binary event-log file for all event classes and severity levels and specifies the binary crash dump file. The following is an example of the default /etc/binlog.conf file:
*.* /usr/adm/binary.errlog dumpfile /usr/adm/crash/binlogdumpfile
The binlogd daemon also creates the /var/run/binlogd.pid, if possible. The file contains a line that specifies the binlogd daemon's process identification number. Use this number to disable or reconfigure the binlogd daemon. To disable the binlogd daemon, send the process a SIGTERM signal. For example:
kill -TERM `cat /var/run/binlogd.pid`
To reconfigure the binlogd daemon, send the process a SIGHUP signal to cause it to read the configuration file again. For example:
kill -HUP `cat /var/run/binlogd.pid`
Processes on the local system also can connect to the binlogd daemon by using a local known socket (/dev/binlogdmb); this is referred to as a "mailbox." When the "mailbox" connection is established, the connected process receives the binary event records that the binlogd processes. The libbinlog.a library provides a set of routines that make using the "mailbox" easy. Refer to the descriptions in /usr/sys/include/dec/binlog/*.h for information on using the "mailbox" programming interface. The uerf command with the -n option utilizes the binlogd "mailbox."
For this release, a number of options are available as described in the following sections. It is recommended that you migrate from uerf to one of these solutions: Compaq Analyze is a reporting tool primarily designed to be used with newer (EV6) processors. Refer to the Compaq Analyze documentation on the Associated Products CD-ROM for information on installation and use. Refer to the dia(8) reference page, or the DECevent documentation on the Associated Products CD-ROM for information on the DECevent Translation and Reporting Utility. binlog is also a channel that is read by the Event Management utility (EVM). Messages are also converted to EVM events and notified to the EVM daemon, using DECevent as the translation mechanism. Refer to the EVM(5) reference page and System Administration for more information on event management. In particular, note that DECevent must be running on remote hosts to receive notification of remote binlog events. The sys_check(8) utility uses translation and reporting tools to read system error files such as binary.errlog.saved.
Command path. Binary configuration file. Process identification number. Name of the "mailbox" socket. Kernel log device.
Commands: logger(1), savecore(8), uerf(8)
System Administration delim off