errord(8) CLIX errord(8)
NAME
errord - Runs error logging daemon
SYNOPSIS
/usr/lib/errord
DESCRIPTION
The errord error logging daemon sends errors directly to the errors report
generator, errors. In addition, it can send error messages to and receive
error messages from remote systems. Another feature of this daemon makes
it possible to selectively log certain error types.
The error log daemon invoked at boot time, errord, posts system errors to
the error log file. Upon its start, the daemon checks for the existence
of the configuration file named /usr/adm/errord.rc. If this file does not
exist, errord assumes the default configuration, which is to log errors to
/usr/adm/errlog, limit the size of the log file to 500 blocks, and log all
reported errors on the local system.
The kernel posts errors to the /dev/errlog file. When an error is posted,
errord reads /dev/errlog and appends the message to the log file. If the
log file does not exist, errord creates it. If the log file becomes
larger than 500 blocks, the daemon renames it /usr/adm/errlog"date", where
date is the current date in the format MMDD. The errord daemon then
creates a new error log file.
The errord daemon can send errors directly to the error report generator,
errors. In addition, it can send error messages to or receive them from
other systems on the network and selectively log error types. See
errord.rc(4) and errconfig(8) for more details on customizing the
configuration of the daemon.
EXAMPLES
This example shows how to start the error daemon.
/etc/init.d/errord start
FILES
/dev/errlog System error log device.
/usr/adm/errlog Default system error log file.
/usr/adm/errord.rc Error daemon configuration file.
/usr/adm/errlog"date" Old system error log file.
2/94 - Intergraph Corporation 1
errord(8) CLIX errord(8)
/etc/hosts The TCP/IP hostname database.
/etc/services The TCP/IP service name database.
CAUTIONS
Transmission Control Protocol/Internet Protocol (TCP/IP) must be running
for the daemon to send or receive errors from other systems.
Only systems with a 4.0 (partition 4, modifier 0) disk partition will log
system starts, stops, asserts, cmn_errs and panics. These types of errors
may not be logged if the systems boots with a large number of errors.
DIAGNOSTICS
All error messages generated by errord appear on the console.
The errord daemon fails to run if it is unable to open /dev/errlog, or if
it cannot open or create a new errlog file. Be sure errord is either
started at boot time or, if started later, is started by root.
If there is any problem in setting up to send or receive errors over the
network, errord displays an error message and accepts local errors only.
(It will not send or receive errors over the network.) If the problem
occurred in setting up to send errors, (``unknown host'') be sure the
specified system to send errors to is in /etc/hosts. For errors
encountered in either sending or receiving over the network, (``unable to
bind to socket,'' ``unable to connect to node'') check to see if the
following line appears in /etc/services:
errord 700/tcp
If errord is sending errors to another error daemon over the network and
the receiving system is busy, the following message appears on the sending
system's console: ``errord: unable to connect to "node", still trying''.
The sending daemon will try three times before giving up trying to send
this particular error. In this case, the error message ``errord: connect
failed'' appears.
RELATED INFORMATION
Commands: errconfig(8), errors(1)
Files: hosts(4), services(4), errord.rc(4)
2 Intergraph Corporation - 2/94