errlog(4) [ultrix man page]

errlog(4)						     Kernel Interfaces Manual							 errlog(4)

Name
       errlog - error logging interface

Description
       This  is  a  special character device that provides an interface to the error logging daemon process, This device is also accessed by other
       system utilities, such as the error log administration utility,

Restrictions
       This device should be readable and writable by root only, to protect access by nonsystem processes.  The  major	number	assigned  to  this
       device must correlate with the corresponding major number designation in the system kernel.

Files
See Also
       MAKEDEV(8)

																	 errlog(4)

binlog.conf(4)						     Kernel Interfaces Manual						    binlog.conf(4)

NAME

       binlog.conf - binlogd configuration file

SYNOPSIS

       event_code.priority	     destination  Where: Are the numeric codes specified in binlog.h and the binlogd(8) reference page.  An aster-
       isk (*) specifies that all events should be selected. The code dumpfile Specifies the recovery of the kernel binary event log buffer from a
       crash  dump.  A	severity  level cannot be specified.  Filters selected events as severe, high, and low. An asterisk (*) specifies that all
       events should be selected.  A local file pathname to a log file, or a remote system hostname for remote logging of events.

DESCRIPTION

       The /etc/binlog.conf file is a system file that enables you to configure or filter events that are to be logged by the binary error logger,
       binlogd.

       The  binlogd  daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to
       include comments in the file or to disable an entry.

       If you want the binlogd daemon to use a configuration file other than the default, specify the file name with the following command: # bin-
       logd  -f config_file Note that EVM subscribes to binlog events by default, and any configuration options you select will affect what events
       are available to EVM. You can filter and select binlog events using EVM utilities, as described in the EVM(5) reference page.

EXAMPLES

       The following is a sample /etc/binlog.conf file: # # binlogd configuration file # #format of a line:   event_code.priority      destination
       #  #  where:  event_code   -  see codes in binlog.h and man page, # * = all events #  priority	 - severe, high, low, * = all priorities #
       destination - local file pathname or remote system #  hostname

       *.*	 /usr/adm/binary.errlog      dumpfile	    /usr/adm/crash/binlogdumpfile      crdlog	      /usr/adm/binary.crdlog	  102.high
       /usr/adm/disk.errlog

FILES

       /etc/binlog.conf
       /etc/binlog.auth - Authorization file for remote logging.
       /usr/sys/include/dec/binlog/binlog.h - Common components of a binary event log record.

RELATED INFORMATION

       Commands: /usr/sbin/binlogd(8), EVM(5)

       System Administration delim off

																    binlog.conf(4)