syslogd - log systems messages

syslogd [-du] [-f config_file] [-m mark_interval] [-a path] [-p log_socket]

syslogd reads and logs messages to the system console, log files, other
machines and/or users as specified by its configuration file.

The options are as follows:

-d
        Enable debugging to the standard output, and do not disassociate
        from the controlling terminal.

-f config_file
        Specify the pathname of an alternate configuration file; the default
        is /etc/syslog.conf.

-m mark_interval
        Select the number of minutes between ``mark'' messages; the default
        is 20 minutes.

-u
        Select the historical ``insecure'' mode, in which syslogd will
        accept input from the UDP port.  Some software wants this, but
        you can be subjected to a variety of attacks over the network,
        including attackers remotely filling logs.

-p log_socket
        Specify the pathname of an alternate log socket to be used instead;
        the default is /dev/log.

-a path
        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.

syslogd reads its configuration file when it starts up and whenever it
receives a hangup signal. For information on the format of the configuration
file, see syslog.conf(5).

Normally syslogd will only use this socket to send messages outwards, but
in ``insecure'' mode it will also read messages from this socket. syslogd
also opens and reads messages from the UNIX domain socket /dev/log, and from
the special device /dev/klog (to read kernel messages).

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
messages.

syslogd creates the file /var/run/syslog.pid, and stores its process ID
there. This can be used to kill or reconfigure syslogd.

The message sent to syslogd should consist of a single line. The message
can contain a priority code, which should be a preceding decimal number
in angle braces, for example, "<5>". This priority code should map into
the priorities defined in the include file .

Files:

	/etc/syslog.conf     configuration file
	/var/run/syslog.pid  process ID of current syslogd
	/dev/klog            kernel log device