Click this button to go to the index for this section.

binlogd(8)
NAME
  binlogd - Binary event-log daemon

SYNOPSIS
  /usr/sbin/binlogd [-d]  [-f config_file]

FLAGS
  -d  Enables debugging.

  -f config_file
      Specifies the alternate binary configuration file.

DESCRIPTION
  The binlogd daemon logs binary event records to the files specified in the
  /etc/binlog.conf configuration file.	You must use the uerf command to
  examine the files.

  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:

  Hardware-Related Events


  100	 CPU machine checks and exceptions

  101	 Memory

  102	 Disks

  103	 Tapes

  104	 Device controllers

  105	 Adapters

  106	 Buses

  107	 Stray interrupts

  108	 Console events

  109	 Stack dumps

  199	 SCSI CAM events

  Software-Detected Events


  201	 CI port-to-port driver events

  202	 System communications services events

  Informational ASCII Messages


  250	 Generic ASCII informational messages

  Operational Events


  300	 ASCII startup messages

  301	 ASCII shutdown messages

  302	 Panic messages

  310	 Timestamp

  350	 Diagnostic status messages

  351	 Repair and maintenance messages

  You can specify the following severity levels:

  severe Specifies events that cannot be recovered and that are usually fatal
	 to system operation.

  high	 Specifies events that either can be recovered or cannot be recovered
	 but are not fatal to system operation.

  low	 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:

  @host

  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."

  Examining the Event-Log File


  Use the uerf command to translate the binary event-log file to ASCII text.
  The uerf command uses the file name destination for the *.* entry in the
  /etc/binlog.conf as the default binary event-log file.  If there is no *.*
  entry or if you do not want to use the default file, use the uerf command
  with the -f filename option to specify the binary event-log file.

FILES
  /usr/sbin/binlogd
	     Command path.

  /etc/binlog.conf
	     Binary configuration file.

  /var/run/binlogd.pid
	     Process identification number.

  /dev/binlogdmb
	     Name of the "mailbox" socket.

  /dev/kbinlog
	     Kernel log device.

RELATED INFORMATION
  Commands: logger(1), savecore(8), uerf(8)

  System Administration