Sun Microsystems Sun Workstation 100U System Manager's Manual page 257

SYSLOG(8)
MAINTENANCE COMMANDS SYSLOG(8)
NAME
syslog - log systems messages
SYNOPSIS
/uar /etc/ln.ayalo.
I
-mN
Il-fname Il-d I
DESCRIPTION
102
51/ 810 9 reads a datagram socket and logs each message it reads into a set of files described by the
configuration file I etcl 81/810g.con/. S1/810g configures when it starts up and whenever it receives a
hangup signal. S1/810g logs to the host specified by 'Ioghost' in the I etcl h08t8 file. For details on
. running 81/810g in a Sun network environment, see the section, "System Log Configuration" in the
S1/stem Set-up and Operation chapter of the S1/8tem In8tallation and Maintenance Guide.
Each message logged consists of one line. A message can contain a priority code, marked by a
digit in angle braces at the beginning of the line. Priorities are defined in
<
syslog.h
>,
as defined
in the list below. LOG_ALERT is prioity 1 (the highest priority) while LOG_DEBUG is priority
g (the lowest priority).
LOG_ALERT this priority should essentially never be used. It applies only to messages that
are so important that every user should be aware of them, for example, a
serious hardware failure.
LOG_EMERG
messages of this priority should be issued only when immediate attention is
needed by a qualified system person, for example, when some valuable system
resource disappears. They get sent to a list of system people.
Emergency messages are not sent to users, but represent major conditions.
An example might be hard disk failures. These could be logged in a separate
file so that critical conditions could be easily scanned.
these represent error conditions, such as soft disk failures, etc.
such messages contain critical information, but which can not be classed as
errors, for example, 'su' attempts. . Messages of this priority and higher are
typically logged on the system console.
issued when an abnormal condition has been detected, but recovery can take
pla.ce.
something that falls in the class of "important information;" this class is
inrormational but important enough that you don't want to throw items in it
away casually. Messages without any priority aBBigned to them are typically
mapped into this priority.
LOG_INFO information level messages. These messages could be thrown away without
problems, but should be included ir you want to keep a close watch on your
system.
LOG_DEBUG it may be userul to log certain debugging inrormation. Normally this will be
thrown away.
It is expected that the kernel will not log anything below LOG_ERR priority.
The 81/8109 configuration file, etcI81/810g.conf, consists of two sections separated by a blank line.
The first section defines files that 81/8109 will log into. Each line contains a single digit which
defines the lowest priority (highest numbered priority) that this file will receive, an optional aster-
isk which guarantees that something gets output at least every 20 minutes, and a pathname. The
second part of the file contains a list of users that will be informed on SALER T level messages.
For example, the configuration file:
s·
Idev I
tty
8
8/usrlspool/a dm /syslog
Last change:
16
February
1984 Sun Release
1.1