NAME
syslogd - Logs system messages
SYNOPSIS
syslogd [-f config_file] [-m mark_interval] [-p pathname]
[-d]
The syslogd daemon reads and logs messages into a set of
files described by the configuration file /etc/syslog.conf.
FLAGS
-d Turns on debugging.
-f config_file
Specifies an alternate configuration file.
-m mark_interval
Selects the number of minutes between mark mes-
sages.
-p pathname
Specifies the alternate device pathname for the
system log device.
DESCRIPTION
Each message is one line. A message can contain a priority
code, marked by a number in angle braces at the beginning of
the line. Priorities are defined in <sys/syslog.h>. sys-
logd reads from the domain socket /dev/log, from an Internet
domain socket specified in /etc/services, and from the spe-
cial device /dev/klog (to read kernel messages).
syslogd configures when it starts up and whenever it
receives a hangup signal. Lines in the configuration file
have a selector to determine the message priorities to which
the line applies and an action. The action field is
separated from the selector by one or more tabs.
Selectors are semicolon separated lists of priority specif-
iers. Each priority has a facility describing the part of
the system that generated the message, a dot, and a level
indicating the severity of the message. Symbolic names may
be used. An * (asterisk) selects all facilities. All mes-
sages of the specified level or higher (greater severity)
are selected. More than one facility may be selected using
commas to separate them. For example:
*.emerg;mail,daemon.crit
This line selects all facilities at the emerg level and the
mail and daemon facilities at the crit level.
Known facilities and levels recognized by syslogd are those
listed in syslog without the leading LOG_. The additional
facility mark has a message at priority LOG_INFO sent to it
every 20 minutes (this may be changed with the -m flag).
The mark facility is not enabled by a facility field con-
taining an * (asterisk). The level none may be used to dis-
able a particular facility. For example:
*.debug;mail.none
sends all messages except mail messages to the selected
file.
The second part of each line describes where the message is
to be logged if this line is selected. There are four
forms:
o A filename (beginning with a leading / (slash)). The
file will be opened in append mode.
o A hostname preceeded by an @ (at sign). Selected mes-
sages are forwarded to the syslogd on the named host.
o A comma separated list of users. Selected messages are
written to those users if they are logged in.
o An * (asterisk). Selected messages are written to all
users who are logged in.
Blank lines and lines beginning with # (number sign) are
ignored.
For example:
kern,mark.debug /dev/console
*.notice;mail.info /var/adm/syslog/mail
*.crit /var/adm/syslog/critical
kern.err @ucbarpa
*.emerg *
*.alert eric,kridle
*.alert;auth.warning ralph
The preceding configuration file logs:
o Logs all kernel messages and 20 minute marks onto the
system console
o Logs all notice (or higher) level messages and all mail
system messages except debug messages into the file
/var/adm/syslog/mail
o Logs all critical messages into the
/var/adm/syslog/critical file
o Forwards kernel messages of error severity or higher to
ucbarpa.
o Informs all users of any emergency messages, informs
users eric and kridle of any alert messages, and
informs user ralph of any alert message or any warning
message (or higher) from the authorization system.
Destinations for logged messages can be specified with full
pathnames (beginning with a leading / [slash]). The syslogd
daemon then opens the specified file(s) in append mode.
Typically, you will want to divert messages separately,
according to facility, into files such as kern.log,
mail.log, lpr.log, and debug.log.
Examining Error Logging Files
The syslogd daemon acts as a central routing facility for
messages whose formats are determined by the programs that
produce them. In other words, the message format for error
messages and status information is not
The syslogd daemon creates the file /var/run/syslog.pid, if
possible, containing a single line with its process ID.
This can be used to kill or reconfigure syslogd.
To bring syslogd down, it should be sent a terminate signal
(for example: kill `cat /var/run/syslog.pid`).
If no syslog.conf configuration file is present, syslogd
uses the following built-in defaults:
*.ERR /dev/console
*.PANIC *
According to these defaults, all error messages are logged
on the console and all panic messages (from the kernel) are
sent to all logged-in users. No files are written. It is
recommended, however, that administrators not use the
built-in defaults, and create a syslog.conf file with the
appropriate specifications.
FILES
/usr/sbin/syslogd
Specifies the command path
/etc/syslog.conf
Configuration file.
/var/run/syslog.pid
Process ID.
/dev/log The name of the domain datagram log socket.
/dev/klog Kernel log device.
RELATED INFORMATION
Functions: syslog(3)
"Error Logging" in the OSF/1 System Administrator's Guide.
Acknowledgement and Disclaimer