HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
syslogd(1M) syslogd(1M)
NAME
syslogd - log system messages
SYNOPSIS
/usr/sbin/syslogd [-a][-d][-D][-f configfile][-m markinterval][-N][-p logfile][-r]
DESCRIPTION
The syslogd command reads and logs messages into a set of files described by the configuration file
/etc/syslog.conf.
Options
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 reconfigure
syslogd.
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 signal:
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 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 res-
tart 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 more tabs.
Selectors are semicolon separated lists of priority specifiers. Each priority has a facility indicating the sub-
system 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 exam-
ple:
*.emerg;mail,daemon.crit
selects all facilitiesat 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 lower-
case 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
HP-UX Release 11i: December 2000 − 1 − Section 1M−−955
___
___