syslogd - log system messages
/usr/sbin/syslogd [-a] [-d] [-D] [-f configfile] [-m markinterval] [-N]
[-p logfile] [-r]
The syslogd command reads and logs messages into a set of files
described by the configuration file /etc/syslog.conf.
syslogd recognizes the following options:
-a Allows all messages except consecutive
duplicate messages without reordering them.
-d Turn on debugging.
-D Prevent the kernel from directly printing its
messages on the system console. In this
case, syslogd is responsible for routing all
kernel messages to their proper destination.
-f configfile Use configfile instead of /etc/syslog.conf.
-m markinterval Wait markinterval minutes between mark
messages, instead of 20 minutes.
-N Don't listen to socket.
-p logfile Use logfile instead of /dev/log.
-r Don't suppress duplicate messages.
syslogd creates the file /var/run/syslog.pid, if possible, containing
a single line with its process ID. This can be used to kill or
To kill syslogd, send it a terminate signal:
kill `cat /var/run/syslog.pid`
To make syslogd, re-read its configuration file, send it a HANGUP
kill -HUP `cat /var/run/syslog.pid`
syslogd collects messages from the UNIX domain socket /dev/log.un, an
Internet domain socket specified in /etc/services, the named pipe
/dev/log, and from the kernel log device /dev/klog. By default, local
Hewlett-Packard Company - 1 - HP-UX Release 11i: November 2000
programs calling syslog() send log messages to the UNIX domain socket
(see syslog(3C)). If UNIX domain sockets are not configured on the
system, they write to the named pipe instead. If INET domain sockets
are not configured, syslogd does not receive messages forwarded from
other hosts, nor does it forward messages (see below).
Each message is one line. A message can contain a priority code and
facility code as the second field of the line. By default, the
priority and facility codes are not logged in log files. To add the
priority and facility codes in the message field, the user has to add
-v in the /etc/rc.config.d/syslogd file and restart the daemon.
Priorities and Facilities are defined in the header file <<<<syslog.h>>>>.
syslogd configures itself when it starts up and whenever it receives a
hangup signal. Lines in the configuration file consist of 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
Selectors are semicolon separated lists of priority specifiers. Each
priority has a facility indicating the subsystem that generated the
message, a dot, and a level indicating the severity of the message.
Symbolic names can be used. An asterisk selects all facilities. All
messages of the specified level or higher (greater severity) are
selected. More than one facility can be selected, using commas to
separate them. For example:
selects all facilities at the emerg level and the mail and daemon
facilities at the crit level.
The known facilities and levels recognized by syslogd are those listed
in syslog(3C) converted to lowercase without the leading LOG_. The
additional facility mark has a message at priority LOG_INFO sent to it
every 20 minutes (this can be changed with the -m flag). The mark
facility is not enabled by a facility field containing an asterisk.
The level none can be used to disable a particular facility. For
selects all messages except mail messages.
The second part of each line describes where the message is to be
logged if this line is selected. There are four forms:
+ A file name (beginning with a leading slash). The file is
opened in append mode. If the file does not exist, it is
Hewlett-Packard Company - 2 - HP-UX Release 11i: November 2000
+ A host name preceded by an @ character. Selected messages are
forwarded to the syslogd on the named host.
+ A comma-separated list of users. Selected messages are
written to those users' terminals if they are logged in.
+ An asterisk. Selected messages are written to the terminals
of all logged-in users.
Blank lines and lines beginning with a # character are ignored.
For example, the configuration file:
logs all kernel messages and 20 minute marks onto the system console,
all mail system messages to /var/adm/syslog/mail.log, and all messages
at info and above, except mail messages, to the file
/var/adm/syslog/syslog.log. Messages at alert and above are logged to
the console and to the users root, eric, and kridle if they are logged
in. emerg messages are written to all logged-in users' terminals, and
forwarded to the host admin.
Only a superuser can invoke syslogd.
A configuration file selector selects all messages at the specified
level or higher. The configuration lines:
cause the logfile to get two copies of all user messages at level info
Kernel panic messages are not sent to syslogd.
All HP-UX kernel messages are treated as if they had the crit priority
If syslogd is invoked with the -D option and syslogd terminates
abnormally, kernel messages will not appear on the system console. In
that case, reinvoke syslogd without the -D option to enable the kernel
to send its messages to the system console.
Hewlett-Packard Company - 3 - HP-UX Release 11i: November 2000
Kernel logging through the special log device /dev/klog is not
The -D option is not supported.
syslogd was developed by the University of California, Berkeley.
/dev/klog The kernel log device
/dev/log The named pipe on which syslogd reads
/dev/log.un The UNIX domain socket on which syslogd
reads log messages
/etc/syslog.conf Configuration file
/var/run/syslog.pid Process ID
Hewlett-Packard Company - 4 - HP-UX Release 11i: November 2000