syslogd - log systems messages
syslogd [-dnu] [-a path] [-f config_file] [-m mark_interval]
[-p log_socket] [-s reporting_socket]
syslogd reads and logs messages to the system console, log
machines and/or users as specified by its configuration
The options are as follows:
Specify a location where syslogd should place an additional log
socket. Up to about 20 additional logging sockets
can be specified.
The primary use for this is to place additional log sockets
in /dev/log of various chroot filespaces.
-d Enable debugging to the standard output, and do not
from the controlling terminal.
Specify the pathname of an alternate configuration
file; the default
Select the number of minutes between ``mark'' messages; the default
is 20 minutes.
-n Print source addresses numerically rather than symbolically.
This saves an address-to-name lookup for each incoming message,
which can be useful when combined with the -u option
on a loghost
with no DNS cache. Messages from the local host
will still be
logged with the symbolic local host name.
Specify the pathname of an alternate log socket to
be used instead;
the default is /dev/log.
Specify path to an AF_LOCAL socket for use in reporting logs
stored in memory buffers using syslogc(8).
-u Select the historical ``insecure'' mode, in which
accept input from the UDP port. Some software wants
you can be subjected to a variety of attacks over
including attackers remotely filling logs.
syslogd reads its configuration file when it starts up and
receives a hangup signal. For information on the format of
file, see syslog.conf(5).
syslogd opens an Internet domain socket as specified in
Normally syslogd will only use this socket to send messages
in ``insecure'' mode it will also read messages from this
syslogd also opens and reads messages from the UNIX domain
/dev/log, and from the special device /dev/klog (to read
syslogd opens the above described socket whether or not it
is running in
secure mode. If syslogd is running in secure mode, all incoming data on
this socket is discarded. The socket is required for sending forwarded
syslogd creates the file /var/run/syslog.pid, and stores its
there. This can be used to kill or reconfigure syslogd.
The message sent to syslogd should consist of a single line.
can contain a priority code, which should be a preceding
in angle braces, for example, ``<5>''. This priority code
should map into
the priorities defined in the include file
/etc/syslog.conf configuration file
/var/run/syslog.pid process ID of current syslogd
/dev/log name of the UNIX domain datagram log
/dev/klog kernel log device
logger(1), syslog(3), services(5), syslog.conf(5), newsyslog(8),
The syslogd command appeared in 4.3BSD.
OpenBSD 3.6 June 6, 1993
[ Back ]