|Main index||Section 8||日本語||Options|
The options are as follows:
|Force syslogd to use IPv4 addresses only.|
|Force syslogd to use IPv6 addresses only.|
|Tells syslogd not to interfere with 8-bit data. Normally syslogd will replace C1 control characters (ISO 8859 and Unicode characters) with their "M- x" equivalent. Note, this option does not change the way syslogd alters control characters (seeiscntrl(3)). They will always be replaced with their "^ x" equivalent.|
|Ordinarily, syslogd tries to send the message to only one address even if the host has more than one A or AAAA record. If this option is specified, syslogd tries to send the message to all addresses.|
to log to this
using UDP datagrams.
The allowed_peer option may be any of the following:
|ipaddr[/ masklen][amp;: service]|
ipaddr[/ prefixlen][amp;: service]Accept datagrams from ipaddr, ipaddr can be specified as an IPv4 address or as an IPv6 address enclosed with ‘amp;[’ and ‘amp;]’. If specified, service is the name or number of an UDP service (see services(5)) the source packet must belong to. A service of ‘amp;*’ accepts UDP packets from any source port. The default service is ‘syslog’. If ipaddr is IPv4 address, a missing masklen will be substituted by the historic class A or class B netmasks if ipaddr belongs into the address range of class A or B, respectively, or by 24 otherwise. If ipaddr is IPv6 address, a missing masklen will be substituted by 128.
|domainname [amp;: service]Accept datagrams where the reverse address lookup yields domainname for the sender address. The meaning of service is as explained above. domainname can contain special characters of a shell-style pattern such as ‘amp;*’.|
| ||Create log files that do not exist (permission is set to‘0600’).|
| ||Disable the compression of repeated instances of the same line into a single line of the form "last message repeated N times" when the output is a pipe to another program. If specified twice, disable this compression in all cases.|
| ||Put syslogd into debugging mode. This is probably only of use to developers working on syslogd.|
| ||Specify the pathname of an alternate configuration file; the default is /etc/syslog.conf.|
| ||Run syslogd in the foreground, rather than going into daemon mode. This is useful if some other process uses fork(2) and exec(3) to run syslogd, and wants to monitor when and how it exits.|
| ||When logging remote messages use hostname from the message (if supplied) instead of using address from which the message was received.|
| ||Disable the translation of messages received with facility "kern" to facility "user". Usually the "kern" facility is reserved for messages read directly from /dev/klog.|
| ||Select the number of minutes between "mark" messages; the default is 20 minutes.|
Disable binding on UDP sockets.
RFC 3164 recommends that outgoing
messages should originate from the privileged port,
the recommended behavior.
This option inherits
| ||Disable DNS query for every request.|
| ||Select the output format of generated log messages. The values bsd and rfc3164 are used to generate RFC 3164 log messages. The values syslog and rfc5424 are used to generate RFC 5424 log messages, having RFC 3339 timestamps with microsecond precision. The default is to generate RFC 3164 log messages.|
| ||Prefix kernel messages with the full kernel boot file as determined by getbootfile(3). Without this, the kernel message prefix is always "kernel:".|
Specify the pathname of an alternate log socket to be used instead;
the default is
When a single
| ||Specify an alternative file in which to store the process ID. The default is /var/run/syslog.pid.|
Specify the pathname of an alternate log socket for privileged
applications to be used instead;
the default is
When a single
| ||Specify a location where syslogd should place an additional log socket. The primary use for this is to place additional log sockets in /var/run/log of various chroot filespaces. File permissions for socket can be specified in octal representation in mode, delimited with a colon. The socket location must be specified as an absolute pathname in path.|
| ||Operate in secure mode. Do not log messages from remote machines. If specified twice, no network socket will be opened at all, which also disables logging to remote machines.|
| ||Always use the local time and date for messages received from the network, instead of the timestamp field supplied in the message by the remote host. This is useful if some of the originating hosts cannot keep time properly or are unable to generate a correct timestamp.|
| ||Unique priority logging. Only log messages at the specified priority. Without this option, messages at the stated priority or higher are logged. This option changes the default comparison from "=>" to "=".|
If specified once,
the numeric facility and priority are
logged with each locally-written message.
If specified more than once,
the names of the facility and priority are logged with each locally-written
This option only affects the formatting of RFC 3164 messages. Messages formatted according to RFC 5424 always include a facility/priority number.
The syslogd utility 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).
The syslogd utility reads messages from the Unix domain sockets /var/run/log and /var/run/logpriv, from an Internet domain socket specified in /etc/services, and from the special device /dev/klog (to read kernel messages).
The syslogd utility creates its process ID file, by default /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 <sys/syslog.h>.
For security reasons,
will not append to log files that do not exist
The date and time are taken from the received message.
If the format of the timestamp field is incorrect,
time obtained from the local host is used instead.
This can be overridden by the
|default process ID file|
|/var/run/log||name of the Unix domain datagram log socket|
|/var/run/logpriv||Unix socket for privileged applications|
|/dev/klog||kernel log device|
The log socket was moved from /dev to ease the use of a read-only root file system. This may confuse some old binaries so that a symbolic link might be used for a transitional period.
|SYSLOGD (8)||July 2, 2018|
|Main index||Section 8||日本語||Options|
|“||I'm not interested in developing a powerful brain. All I'm after is just a mediocre brain, something like the President of the American Telephone and Telegraph Company.||”|
|— Alan Turing|