Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

elcsd(8) [ultrix man page]

elcsd(8)						      System Manager's Manual							  elcsd(8)

       elcsd - error logging daemon


       The  daemon  logs  hardware  and system-related error packets, or error messages, from the kernel errorlog buffer to the file syserr.<host-
       name>.  Hostname is the name of the local system.  At system startup, the daemon is invoked out of For further information, see The  daemon
       must be running whenever the system is in multiuser mode.

       To invoke the daemon in single-user mode, use the command with the -s option.

       You  can  configure  the daemon to log error packets locally from a remote ULTRIX host, or you can configure the daemon to send local error
       packets to a remote system.  Do this by changing the entries in the file.  For further information, see The daemon uses an  internet  data-
       gram socket to log information across systems.

       Parameters  related  to	such as the desired location for the errorlog file or files, as well as instructions for local and remote logging,
       can be specified in the error logging configuration file, For further information, see

       You must have superuser privileges to invoke the daemon.

       The daemon logs general status and error messages to in multiuser mode.	This file is purged whenever the daemon is restarted.

See Also
       elcsd.conf(5), eli(8), rc(8), uerf(8)
       Guide to the Error Logger

4th Berkeley Distribution														  elcsd(8)

Check Out this Related Man Page

elcsd.conf(5)							File Formats Manual						     elcsd.conf(5)

       elcsd.conf - error logging configuration file

       The  file  contains information used by the daemon to configure error logging for the system.  The system manager maintains this file.  The
       error logging daemon is dependent on the current order of the entries in the file.  Do not change the order.

       The information in the file shows any defaults and describes what you can enter.  A newline is used to delimit each entry in  the  file,  a
       null entry consists of a newline alone, and comments begin with #.
       #    elcsd - errlog configuration file

       {	   # delimiter DON'T remove or comment out!
       1	   # status 1-local,2-logrem,4-remlog,5-remlog+priloglocal
		   # errlog file size limit num. of blocks
       /usr/adm/syserr # errlog dir. path
		   # backup errlog dir. path
       /	   # single user errlog dir. path
       /usr/adm/syserr # log remote hosts errlog dir. path
		   # remote hostname to log to
       }	   # delimiter DON'T remove or comment out!
       #  hosts to log :S - separate file or :R - remotes file (together)
       #remote3:S	   # disabled
       The status line of the file describes where you can log error packets, also called error messages:

	    Logs error packets locally =
		   1, the default.

	    Logs error packets from a remote system or systems to the local machine =

	    Logs local and remote error packets locally =

	    Logs error packets from the local system to a remote system =

	    Logs error packets from the local system remotely and logs high
		   priority messages locally = 5.

       The  errorlog  file  size  defines  the	maximum size of an errorlog file.  If disk space is limited, you can specify the maximum number of
       blocks (512 bytes each) you want the errorlog file to be.  If you do not specify the maximum number of blocks, the system will  notify  you
       when the file system is 98% full.

       The  default  errorlog  directory path is You can direct error packets to a different directory; if you do, you must change the default for
       also. For further information, see

       If the error-logging daemon cannot write to the primary errorlog directory path, it attempts to log to the backup errorlog  directory  path

       The  root  directory  is  the default for the single-user errorlog directory path.  When the system makes the transition to multiuser mode,
       errors logged in single-user mode are transferred to the default errorlog directory path  You  can  direct  single-user	error  packets	to
       another directory.

       To log error packets from a remote system locally, set up an errorlog directory path on the local system.  The default is

       Errorlog  packets  from	remote systems can be logged to separate files or to one file.	S sets up a separate errorlog file for each remote
       system that logs locally.  R logs packets from the corresponding remote system to the file syserr.remotes.  The default is S.

       You must have superuser privileges to change the file.  However, anyone can view the file.

       elcsd daemon messages

See Also
       elcsd(8), eli(8), uerf(8)
       Guide to the Error Logger System

Man Page