2019-12-09 22:59:59 +05:30
|
|
|
.\" -*- nroff -*-
|
2019-12-07 15:19:36 +05:30
|
|
|
.\" Copyright (c) 1983, 1986, 1991, 1993
|
2019-12-09 22:59:59 +05:30
|
|
|
.\" The Regents of the University of California.
|
|
|
|
.\" All rights reserved.
|
2019-10-30 20:26:30 +05:30
|
|
|
.\"
|
2019-12-07 15:19:36 +05:30
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
.\" 3. Neither the name of the University nor the names of its contributors
|
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
.\" without specific prior written permission.
|
2019-10-30 20:26:30 +05:30
|
|
|
.\"
|
2019-12-07 15:19:36 +05:30
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
|
|
|
.\" @(#)syslogd.8 8.1 (Berkeley) 6/6/93
|
|
|
|
.\" $FreeBSD$
|
|
|
|
.\"
|
2021-05-05 08:43:31 +05:30
|
|
|
.Dd May 5, 2021
|
2019-12-07 15:19:36 +05:30
|
|
|
.Dt SYSLOGD 8
|
2021-02-21 19:25:17 +05:30
|
|
|
.Os sysklogd
|
2019-10-30 20:26:30 +05:30
|
|
|
.Sh NAME
|
|
|
|
.Nm syslogd
|
2019-12-07 15:19:36 +05:30
|
|
|
.Nd log systems messages
|
2019-10-30 20:26:30 +05:30
|
|
|
.Sh SYNOPSIS
|
|
|
|
.Nm
|
2022-03-08 01:21:42 +05:30
|
|
|
.Op Fl ?468AdFHKknsTtv
|
2019-12-07 17:06:14 +05:30
|
|
|
.Op Fl a Ar addr[/len][:port]
|
|
|
|
.Op Fl a Ar name[:port]
|
|
|
|
.Op Fl b Ar addr[:port]
|
|
|
|
.Op Fl b Ar :port
|
2021-07-01 02:09:09 +05:30
|
|
|
.Op Fl C Ar file
|
2019-12-07 17:06:14 +05:30
|
|
|
.Op Fl f Ar file
|
|
|
|
.Op Fl m Ar interval
|
|
|
|
.Op Fl P Ar file
|
|
|
|
.Op Fl p Ar sock
|
|
|
|
.Op Fl r Ar size[:count]
|
2019-10-30 20:26:30 +05:30
|
|
|
.Sh DESCRIPTION
|
2019-12-07 15:19:36 +05:30
|
|
|
The
|
2019-10-30 20:26:30 +05:30
|
|
|
.Nm
|
2019-12-07 17:06:14 +05:30
|
|
|
utility reads and logs messages to the system console, log files, other
|
2019-12-07 15:19:36 +05:30
|
|
|
machines and/or users as specified by its configuration file.
|
2019-11-03 16:49:57 +05:30
|
|
|
.Pp
|
2019-12-07 17:06:14 +05:30
|
|
|
.Nm
|
|
|
|
support RFC3164 and RFC5424 style log messages for both local and remote
|
|
|
|
logging using Internet and UNIX domain sockets. Differences in style is
|
|
|
|
shown below.
|
|
|
|
.Pp
|
|
|
|
.Bl -tag -compact -width "RFC3164:"
|
2019-12-09 22:54:23 +05:30
|
|
|
.It Sy RFC3164:
|
|
|
|
.Li Aug 24 05:14:15 192.0.2.1 myproc[8710]: Kilroy was here.
|
|
|
|
.It Sy RFC5424:
|
|
|
|
.Li 2003-08-24T05:14:15.000003-07:00 192.0.2.1 myproc 8710 - - Kilroy was here.
|
2019-12-07 17:06:14 +05:30
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
Note, for remote logging the messages are prefixed with
|
2019-12-09 22:50:03 +05:30
|
|
|
.Ql <PRI>
|
2019-12-07 17:06:14 +05:30
|
|
|
or
|
2019-12-09 22:50:03 +05:30
|
|
|
.Ql <PRI>1 ,
|
2019-12-07 17:06:14 +05:30
|
|
|
respectively.
|
|
|
|
.Pp
|
|
|
|
.Nm
|
|
|
|
is derived from BSD sources, today
|
|
|
|
.Fx
|
|
|
|
is the reference for
|
|
|
|
.Nm
|
|
|
|
and
|
|
|
|
.Nx
|
|
|
|
for the new
|
|
|
|
.Xr syslogp 3
|
|
|
|
API, which fully supports the new features of RFC5424. Please note; 1)
|
|
|
|
the intention is to follow standard BSD
|
|
|
|
.Nm
|
|
|
|
behavior, 2) despite having a stand-alone
|
|
|
|
.Xr syslog 3 ,
|
|
|
|
and
|
|
|
|
.Xr syslogp 3
|
2021-02-21 19:41:08 +05:30
|
|
|
API in libsyslog,
|
2019-12-07 17:06:14 +05:30
|
|
|
.Nm
|
|
|
|
interacts transparently with the standard C library
|
|
|
|
.Xr syslog 3
|
|
|
|
API, as implemented in GLIBC, musl libc, and uClibc.
|
|
|
|
.Pp
|
|
|
|
When
|
|
|
|
.Nm
|
|
|
|
starts up it reads its main configuration file
|
|
|
|
.Pa /etc/syslog.conf ,
|
|
|
|
or an alternate file given with the
|
|
|
|
.Fl f Ar file
|
|
|
|
option. For details on how to configure syslog priority
|
|
|
|
(facility.severity) filtering, see
|
|
|
|
.Xr syslog.conf 5 .
|
|
|
|
.Sh OPTIONS
|
|
|
|
By default,
|
|
|
|
.Nm
|
|
|
|
reads messages from the
|
|
|
|
.Ux
|
|
|
|
domain socket
|
|
|
|
.Pa /dev/log ,
|
|
|
|
from an Internet domain socket specified in
|
|
|
|
.Pa /etc/services ,
|
|
|
|
and from
|
2020-09-01 00:48:17 +05:30
|
|
|
.Pa /dev/kmsg
|
2019-12-07 17:06:14 +05:30
|
|
|
.Pq to read kernel messages .
|
|
|
|
The command line options defined below can be used to change this
|
|
|
|
behavior.
|
|
|
|
.Pp
|
2019-12-07 15:19:36 +05:30
|
|
|
The options are as follows:
|
|
|
|
.Bl -tag -width indent
|
2019-10-30 20:26:30 +05:30
|
|
|
.It Fl 4
|
|
|
|
Force
|
|
|
|
.Nm
|
|
|
|
to use IPv4 addresses only.
|
|
|
|
.It Fl 6
|
|
|
|
Force
|
|
|
|
.Nm
|
|
|
|
to use IPv6 addresses only.
|
2022-03-08 01:21:42 +05:30
|
|
|
.It Fl 8
|
|
|
|
Tells
|
|
|
|
.Nm
|
|
|
|
not to interfere with 8-bit data. Normally
|
|
|
|
.Nm
|
|
|
|
replaces C1 control characters
|
|
|
|
.Pq ISO 8859 and Unicode characters
|
|
|
|
with their
|
|
|
|
.Dq M- Ns Em x
|
|
|
|
equivalent. Note, this option does not change the way
|
|
|
|
.Nm
|
|
|
|
alters control characters
|
|
|
|
.Pq see Xr iscntrl 3 .
|
|
|
|
They are always replaced with their
|
|
|
|
.Dq ^ Ns Em x
|
|
|
|
equivalent.
|
2019-10-30 20:26:30 +05:30
|
|
|
.It Fl A
|
|
|
|
Ordinarily,
|
|
|
|
.Nm
|
2019-12-07 15:19:36 +05:30
|
|
|
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,
|
2019-10-30 20:26:30 +05:30
|
|
|
.Nm
|
|
|
|
tries to send the message to all addresses.
|
2022-03-06 05:19:25 +05:30
|
|
|
.It Fl a Ar peer
|
2019-12-07 17:06:14 +05:30
|
|
|
Allow peers to log to this syslogd using UDP datagrams. Multiple
|
2019-11-13 19:02:54 +05:30
|
|
|
.Fl a
|
2019-12-07 17:06:14 +05:30
|
|
|
options may be specified. Any
|
|
|
|
.Fl a
|
|
|
|
option is ignored if the
|
|
|
|
.Fl s
|
|
|
|
option is also specified.
|
2019-12-07 15:19:36 +05:30
|
|
|
.Pp
|
2022-03-06 05:19:25 +05:30
|
|
|
The
|
|
|
|
.Ar peer
|
|
|
|
argument may be any of the following:
|
2019-12-07 17:06:14 +05:30
|
|
|
.Bl -tag -width 'address[/len][:service]'
|
2022-03-06 05:19:25 +05:30
|
|
|
.It address[/len][:service]
|
2019-12-07 17:06:14 +05:30
|
|
|
Accept datagrams from IP
|
|
|
|
.Ar address ,
|
|
|
|
which can be specified as an IPv4 address or as an IPv6 address enclosed
|
|
|
|
with
|
|
|
|
.Sq \&[
|
2019-11-13 19:02:54 +05:30
|
|
|
and
|
2019-12-07 17:06:14 +05:30
|
|
|
.Sq \&] .
|
|
|
|
If specified, service is the name or port number of an UDP service (see
|
2019-11-13 19:02:54 +05:30
|
|
|
.Xr services 5 )
|
2019-12-07 17:06:14 +05:30
|
|
|
the source packet must belong to. A service of
|
|
|
|
.Ql *
|
|
|
|
accepts UDP packets from any source port. The default service is
|
2019-11-13 19:02:54 +05:30
|
|
|
.Ql syslog .
|
|
|
|
If
|
2019-12-07 17:06:14 +05:30
|
|
|
.Ar address
|
|
|
|
is an IPv4 address, a missing prefix
|
|
|
|
.Ar len
|
2019-11-13 19:02:54 +05:30
|
|
|
will be substituted by the historic class A or class B netmasks if
|
2019-12-07 17:06:14 +05:30
|
|
|
.Ar address
|
|
|
|
belongs in the address range of class A or B, respectively, or by'
|
|
|
|
.Ar /24
|
|
|
|
otherwise. If
|
|
|
|
.Ar address
|
|
|
|
is an IPv6 address, a missing prefix
|
|
|
|
.Ar len
|
2019-11-13 19:02:54 +05:30
|
|
|
will be substituted by 128.
|
2022-03-06 05:19:25 +05:30
|
|
|
.It domainname[:service]
|
2019-11-13 19:02:54 +05:30
|
|
|
Accept datagrams where the reverse address lookup yields
|
|
|
|
.Ar domainname
|
2019-12-07 17:06:14 +05:30
|
|
|
for the sender address. The meaning of
|
2019-11-13 19:02:54 +05:30
|
|
|
.Ar service
|
|
|
|
is as explained above.
|
|
|
|
.Ar domainname
|
|
|
|
can contain special characters of a shell-style pattern such as
|
2019-12-07 17:06:14 +05:30
|
|
|
.Ql * .
|
2019-11-13 19:02:54 +05:30
|
|
|
.El
|
2022-03-06 05:19:25 +05:30
|
|
|
.It Fl b Ar name
|
|
|
|
Bind to a specific address and/or port. By default,
|
|
|
|
.Nm
|
|
|
|
listens on all interfaces on UDP port 514, unless started with the
|
|
|
|
.Fl s
|
|
|
|
option. Multiple
|
2019-12-07 15:19:36 +05:30
|
|
|
.Fl b
|
2022-03-06 05:19:25 +05:30
|
|
|
options may be specified to bind to several addresses and/or ports.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Ar name
|
|
|
|
argument may be any of the following:
|
|
|
|
.Bl -tag -width 'address[/len][:service]'
|
|
|
|
.It address[:port]
|
|
|
|
The address can be specified as a hostname or an IP address, and the
|
|
|
|
port as a service name or port number. If an IPv6 address is specified,
|
|
|
|
it should be enclosed with
|
2019-12-07 15:19:36 +05:30
|
|
|
.Ql \&[
|
2019-11-12 16:36:21 +05:30
|
|
|
and
|
2019-12-07 15:19:36 +05:30
|
|
|
.Ql \&] .
|
2022-03-06 05:19:25 +05:30
|
|
|
.It :port
|
|
|
|
Service name or UDP port number. The default service is
|
|
|
|
.Ql syslog
|
|
|
|
(UDP), port 512.
|
|
|
|
.El
|
2021-07-01 02:09:09 +05:30
|
|
|
.It Fl C Ar file
|
|
|
|
File to use for caching last read kernel sequence number from
|
|
|
|
.Pa /dev/kmsg ,
|
|
|
|
default:
|
|
|
|
.Pa /run/syslogd.cache .
|
|
|
|
If
|
|
|
|
.Nm
|
|
|
|
cannot write to, or read from, this file it will cause repeated kernel
|
|
|
|
log messages when restarting
|
|
|
|
.Nm .
|
2021-07-26 17:34:45 +05:30
|
|
|
.Pp
|
|
|
|
.Sy Note:
|
|
|
|
.Nm
|
|
|
|
relies on this file being removed at system reboot. The default
|
|
|
|
location depends on the system and how
|
|
|
|
.Nm
|
|
|
|
was configured.
|
2019-10-30 20:26:30 +05:30
|
|
|
.It Fl d
|
2019-12-07 15:19:36 +05:30
|
|
|
Put
|
2019-10-30 20:26:30 +05:30
|
|
|
.Nm
|
2019-12-07 15:19:36 +05:30
|
|
|
into debugging mode.
|
|
|
|
This is probably only of use to developers working on
|
|
|
|
.Nm .
|
2019-12-09 15:33:06 +05:30
|
|
|
See the
|
|
|
|
.Sx DEBUGGING
|
|
|
|
section for more information.
|
|
|
|
.It Fl f Ar file
|
|
|
|
Specify the path name of an alternate configuration file;
|
2019-12-07 15:19:36 +05:30
|
|
|
the default is
|
2019-10-30 20:26:30 +05:30
|
|
|
.Pa /etc/syslog.conf .
|
2019-12-07 15:19:36 +05:30
|
|
|
.It Fl F
|
|
|
|
Run
|
|
|
|
.Nm
|
|
|
|
in the foreground,
|
|
|
|
rather than going into daemon mode.
|
|
|
|
This is useful if some other process uses
|
|
|
|
.Xr fork 2
|
|
|
|
and
|
|
|
|
.Xr exec 3
|
|
|
|
to run
|
|
|
|
.Nm ,
|
|
|
|
and wants to monitor when and how it exits.
|
2021-11-09 23:02:49 +05:30
|
|
|
.It Fl H
|
|
|
|
When logging remote messages use hostname from the message (if supplied)
|
|
|
|
instead of using address from which the message was received.
|
2022-02-14 04:10:06 +05:30
|
|
|
.It Fl K
|
|
|
|
Disable kernel logging. Useful in container use-cases where kernel logs
|
|
|
|
har handled by the host system.
|
2019-11-13 21:14:51 +05:30
|
|
|
.It Fl k
|
2019-12-07 15:19:36 +05:30
|
|
|
Disable the translation of
|
|
|
|
messages received with facility
|
|
|
|
.Dq kern
|
|
|
|
to facility
|
|
|
|
.Dq user .
|
2019-11-13 21:14:51 +05:30
|
|
|
Usually the
|
2019-12-07 15:19:36 +05:30
|
|
|
.Dq kern
|
|
|
|
facility is reserved for messages read directly from
|
2020-09-01 00:48:17 +05:30
|
|
|
.Pa /dev/kmsg .
|
2019-12-09 15:33:06 +05:30
|
|
|
.It Fl m Ar interval
|
2019-12-07 15:19:36 +05:30
|
|
|
Select the number of minutes between
|
|
|
|
.Dq mark
|
2019-12-09 15:33:06 +05:30
|
|
|
messages; the default is 20 minutes. Setting this to zero disables log
|
|
|
|
marks.
|
2019-11-13 21:46:51 +05:30
|
|
|
.It Fl n
|
|
|
|
Disable DNS query for every request.
|
2019-12-09 15:33:06 +05:30
|
|
|
.It Fl p Ar socket
|
|
|
|
Specify the path name of an alternate log socket to be used instead;
|
2019-12-07 15:19:36 +05:30
|
|
|
the default is
|
2019-12-07 17:06:14 +05:30
|
|
|
.Pa /dev/log .
|
2019-11-07 22:16:15 +05:30
|
|
|
When a single
|
|
|
|
.Fl p
|
2019-12-09 15:33:06 +05:30
|
|
|
option is specified, the default path name is replaced with the
|
|
|
|
specified one. When two or more
|
2019-11-07 22:16:15 +05:30
|
|
|
.Fl p
|
2019-12-09 15:33:06 +05:30
|
|
|
options are specified, the remaining path names are treated as
|
|
|
|
additional log sockets.
|
|
|
|
.It Fl P Ar file
|
2019-12-07 15:19:36 +05:30
|
|
|
Specify an alternative file in which to store the process ID.
|
|
|
|
The default is
|
2021-05-05 08:43:31 +05:30
|
|
|
.Pa /var/run/syslogd.pid .
|
2019-12-09 15:33:06 +05:30
|
|
|
.It Fl r Ar size[:count]
|
|
|
|
Enable built-in support for log rotation of files listed in
|
|
|
|
.Pa /etc/syslog.conf .
|
|
|
|
This feature is particularly useful for small and embedded systems that
|
|
|
|
do not want the overhead of
|
|
|
|
.Xr cron 8
|
|
|
|
and
|
|
|
|
.Xr logrotate 8 .
|
|
|
|
.Pp
|
|
|
|
The option controls the max size and number of backup files kept by the
|
|
|
|
built-in log-rotation. When present on the command line it activates
|
|
|
|
log rotation of all files with the given maximum size. It is also
|
|
|
|
possible to control log rotate per log file, see
|
|
|
|
.Xr syslog.conf 5
|
|
|
|
for details.
|
|
|
|
.Pp
|
|
|
|
The size argument takes optional modifiers; k, M, G. E.g., 100M is
|
|
|
|
100 MiB, 42k is 42 kiB, etc.
|
|
|
|
.Pp
|
|
|
|
The optional number of files kept include both gzipped files and the
|
|
|
|
first rotated (not zipped) file. The default for this, when omitted,
|
|
|
|
is 5.
|
2019-11-12 17:23:21 +05:30
|
|
|
.It Fl s
|
2019-12-07 17:06:14 +05:30
|
|
|
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.
|
2022-05-23 01:25:46 +05:30
|
|
|
.Pp
|
|
|
|
Secure mode can also be set in
|
|
|
|
.Xr syslog.conf 5
|
|
|
|
using the
|
|
|
|
.Cm secure_mode
|
|
|
|
config option. This is more flexible since you can change the option
|
|
|
|
and simply send
|
|
|
|
.Ar SIGHUP
|
|
|
|
to activate the changes, instead of having to restart
|
|
|
|
.Nm .
|
|
|
|
.Pp
|
|
|
|
.Sy Note:
|
|
|
|
the command line option always wins, so it must be removed for
|
|
|
|
.Nm
|
|
|
|
to consider the .conf file option instead.
|
2019-11-13 20:46:23 +05:30
|
|
|
.It Fl T
|
2019-12-07 15:19:36 +05:30
|
|
|
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.
|
2022-02-14 03:21:55 +05:30
|
|
|
.It Fl t
|
|
|
|
Keep (trust) kernel timestamp.
|
|
|
|
.Pp
|
|
|
|
On Linux systems the
|
|
|
|
.Pa /dev/kmsg
|
|
|
|
timestamp is a monotonic clock, in microseconds, relative to the boot of
|
|
|
|
the system. This timestamp is, among other things,
|
|
|
|
.Sy not
|
|
|
|
adjusted for suspend/resume cycles, meaning the kernel logs can start to
|
|
|
|
go out of sync with the rest of the system. This in turn can make it
|
|
|
|
really hard to correlate events.
|
|
|
|
.Pp
|
|
|
|
.Nm
|
|
|
|
by default only trusts the kernel timestamp when starting up the first
|
|
|
|
time. As soon as the the kernel ring buffer has been emptied,
|
|
|
|
.Nm
|
|
|
|
uses its own current time for each received kernel log message. This
|
|
|
|
option disables that behavior.
|
2019-10-30 20:26:30 +05:30
|
|
|
.It Fl v
|
2021-06-22 02:54:18 +05:30
|
|
|
Show program version and exit.
|
2019-12-07 15:19:36 +05:30
|
|
|
.El
|
2019-10-30 20:26:30 +05:30
|
|
|
.Pp
|
2019-12-07 15:19:36 +05:30
|
|
|
The
|
2019-10-30 20:26:30 +05:30
|
|
|
.Nm
|
2019-12-07 15:19:36 +05:30
|
|
|
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
|
|
|
|
.Xr syslog.conf 5 .
|
2019-10-30 20:26:30 +05:30
|
|
|
.Pp
|
2019-12-07 15:19:36 +05:30
|
|
|
The
|
2019-10-30 20:26:30 +05:30
|
|
|
.Nm
|
2019-12-07 15:19:36 +05:30
|
|
|
utility creates its process ID file,
|
|
|
|
by default
|
2021-05-05 08:43:31 +05:30
|
|
|
.Pa /var/run/syslogd.pid ,
|
2019-12-07 17:06:14 +05:30
|
|
|
and stores its process ID there. This can be used to kill or
|
|
|
|
reconfigure
|
2019-12-07 15:19:36 +05:30
|
|
|
.Nm .
|
2019-10-30 20:26:30 +05:30
|
|
|
.Pp
|
2019-12-07 15:19:36 +05:30
|
|
|
The message sent to
|
|
|
|
.Nm
|
2019-12-07 17:06:14 +05:30
|
|
|
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,
|
2019-12-07 15:19:36 +05:30
|
|
|
.Sq Aq 5 .
|
|
|
|
This priority code should map into the priorities defined in the
|
|
|
|
include file
|
|
|
|
.In sys/syslog.h .
|
2019-12-07 17:06:14 +05:30
|
|
|
To log with RFC5424 style messages the priority code must be directly
|
2021-02-21 19:41:08 +05:30
|
|
|
followed by the version number, this is all handled by libsyslog, which
|
|
|
|
is the
|
2019-12-07 17:06:14 +05:30
|
|
|
.Nx
|
|
|
|
.Xr syslogp 3
|
|
|
|
API included with the
|
|
|
|
.Nm sysklogd
|
|
|
|
project.
|
2019-12-07 15:19:36 +05:30
|
|
|
.Pp
|
2019-12-07 17:06:14 +05:30
|
|
|
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
|
2019-12-07 15:19:36 +05:30
|
|
|
.Fl T
|
2019-11-15 14:10:37 +05:30
|
|
|
flag.
|
2019-12-09 15:33:06 +05:30
|
|
|
.Sh SECURITY
|
|
|
|
There are a number of methods of protecting a machine:
|
|
|
|
.Bl -enum
|
|
|
|
.It
|
|
|
|
Disabling inet domain sockets will limit risk to the local machine. Use
|
|
|
|
the secure mode flag
|
|
|
|
.Fl s
|
|
|
|
for this.
|
|
|
|
.It
|
|
|
|
When secure mode cannot be used, only allow certain remote peers using
|
|
|
|
the
|
|
|
|
.Fl a Ar PEER
|
|
|
|
flag.
|
|
|
|
.It
|
|
|
|
Implement kernel firewalling to limit which hosts or networks have
|
|
|
|
access to the 514/UDP socket.
|
|
|
|
.It
|
|
|
|
Logging can be directed to an isolated or non-root filesystem which,
|
|
|
|
if filled, will not impair the machine.
|
|
|
|
.It
|
|
|
|
Most modern UNIX filesystems can be configured to limit a certain
|
|
|
|
percentage of a filesystem to usage by root only.
|
|
|
|
.El
|
|
|
|
.Sh DEBUGGING
|
|
|
|
When debug mode
|
|
|
|
.Fl ( d )
|
|
|
|
is enabled
|
|
|
|
.Nm
|
|
|
|
only the first
|
|
|
|
.Fn init
|
|
|
|
is shown.
|
|
|
|
.Nm
|
|
|
|
then prompts you to send
|
|
|
|
.Ar SIGUSR1
|
|
|
|
to continue debugging. The output is very verbose and is probably only
|
|
|
|
useful to developers.
|
|
|
|
.Pp
|
|
|
|
When
|
|
|
|
.Nm
|
|
|
|
receives
|
|
|
|
.Ar SIGHUP
|
|
|
|
it reloads its configuration file, and at the end of the
|
|
|
|
.Fn init
|
|
|
|
sequence all log targets are listed with their respective priority per
|
|
|
|
facility, the action and the log format used:
|
|
|
|
.Pp
|
|
|
|
.Bl -tag -width priority
|
|
|
|
.It priority
|
|
|
|
Bit mapped priorities listed per facility, one priority per facility,
|
|
|
|
starting with kernel as the left-most column.
|
|
|
|
.It action
|
|
|
|
FILE, remote sink (FORW), WALL, etc. See
|
|
|
|
.Xr syslog.conf 5
|
|
|
|
for details.
|
|
|
|
.It args
|
|
|
|
The action argument and the log format used. E.g., for FILE actions the
|
|
|
|
log filename, for FORW action the remote host:port. The format is one
|
|
|
|
of; BSD, RFC5424, or RFC3164. The latter is the default except for FORW
|
|
|
|
actions.
|
|
|
|
.El
|
|
|
|
.Sh SIGNALS
|
|
|
|
.Nm
|
|
|
|
supports the following signals:
|
|
|
|
.Pp
|
|
|
|
.Bl -tag -width "TERM, QUIT"
|
|
|
|
.It HUP
|
|
|
|
This lets
|
|
|
|
.Nm
|
|
|
|
perform a re-initialization. All open files are closed, the
|
|
|
|
configuration file (see above) is reread and the
|
|
|
|
.Xr syslog 3
|
|
|
|
facility is started again.
|
|
|
|
.It TERM
|
|
|
|
This tells
|
|
|
|
.Nm
|
|
|
|
to exit gracefully. Flushing any log files to disk.
|
|
|
|
.It INT, QUIT
|
|
|
|
In debug mode these are ignored. In normal operation they act as
|
|
|
|
SIGTERM.
|
|
|
|
.It USR1
|
|
|
|
In debug mode this switches debugging on/off. In normal operation
|
|
|
|
it is ignored.
|
2022-01-20 19:04:51 +05:30
|
|
|
.It USR2
|
|
|
|
.Nm
|
|
|
|
will rotate all files for which rotation is configured when receiving
|
|
|
|
this signal.
|
2019-12-09 15:33:06 +05:30
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
For convenience the PID is by default stored in
|
|
|
|
.Pa /var/run/syslogd.pid .
|
|
|
|
A script can look for the existence of this file to determine if
|
|
|
|
.Nm
|
|
|
|
is running, and then send signals:
|
|
|
|
.Bd -literal -offset indent
|
|
|
|
kill -SIGNAL `cat /var/run/syslogd.pid`
|
|
|
|
.Ed
|
2019-10-30 20:26:30 +05:30
|
|
|
.Sh FILES
|
2019-12-07 17:06:14 +05:30
|
|
|
.Bl -tag -width /etc/syslog.d/50-default.conf -compact
|
2019-10-30 20:26:30 +05:30
|
|
|
.It Pa /etc/syslog.conf
|
2019-12-07 17:06:14 +05:30
|
|
|
configuration file. See
|
|
|
|
.Xr syslog.conf 5
|
|
|
|
for more information.
|
|
|
|
.It Pa /etc/syslog.d/*.conf
|
2021-05-05 08:43:31 +05:30
|
|
|
conventional sub-directory of
|
2019-12-07 17:06:14 +05:30
|
|
|
.Pa .conf
|
|
|
|
files read by
|
|
|
|
.Nm .
|
|
|
|
.It Pa /etc/syslog.d/50-default.conf
|
2021-05-05 08:43:31 +05:30
|
|
|
conventional name for default rules.
|
|
|
|
.It Pa /var/run/syslogd.pid
|
2019-12-07 15:19:36 +05:30
|
|
|
default process ID file
|
2021-05-05 08:43:31 +05:30
|
|
|
.It Pa /var/run/syslogd.cache
|
|
|
|
cache of last read sequence number from
|
2021-07-26 17:34:45 +05:30
|
|
|
.Pa /dev/kmsg .
|
|
|
|
Please note,
|
|
|
|
.Nm
|
|
|
|
relies on this file being removed at system reboot.
|
2019-12-07 17:06:14 +05:30
|
|
|
.It Pa /dev/log
|
2019-12-07 15:19:36 +05:30
|
|
|
name of the
|
|
|
|
.Ux
|
|
|
|
domain datagram log socket
|
2020-09-01 00:48:17 +05:30
|
|
|
.It Pa /dev/kmsg
|
2019-12-07 15:19:36 +05:30
|
|
|
kernel log device
|
2019-10-30 20:26:30 +05:30
|
|
|
.El
|
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr logger 1 ,
|
2019-12-07 15:19:36 +05:30
|
|
|
.Xr syslog 3 ,
|
2019-12-07 17:06:14 +05:30
|
|
|
.Xr syslogp 3 ,
|
2019-10-30 20:26:30 +05:30
|
|
|
.Xr services 5 ,
|
2019-12-07 15:19:36 +05:30
|
|
|
.Xr syslog.conf 5 ,
|
|
|
|
.Sh HISTORY
|
2019-10-30 20:26:30 +05:30
|
|
|
.Nm
|
2019-12-09 15:33:06 +05:30
|
|
|
was originally ported to Linux by
|
2019-12-07 17:06:14 +05:30
|
|
|
.An Greg Wettstein Aq Mt greg@wind.enjellic.com
|
2019-12-09 15:33:06 +05:30
|
|
|
and the project was named
|
2019-12-07 17:06:14 +05:30
|
|
|
.Nm sysklogd
|
|
|
|
when a separate log daemon,
|
|
|
|
.Nm klogd ,
|
2019-12-09 22:50:28 +05:30
|
|
|
for Linux kernel messages was added.
|
|
|
|
.Pp
|
|
|
|
It was the default
|
2019-12-07 17:06:14 +05:30
|
|
|
.Nm
|
|
|
|
in Debian and Ubuntu, maintained by
|
|
|
|
.An Martin Schulze Aq Mt joey@infodrom.org ,
|
|
|
|
who fixed some bugs and added several new features. When Debian replaced
|
|
|
|
.Nm sysklogd
|
|
|
|
with
|
|
|
|
.Nm rsyslogd
|
2019-12-09 22:50:28 +05:30
|
|
|
the project was abandoned.
|
|
|
|
.Pp
|
|
|
|
In 2018
|
2020-09-01 00:58:25 +05:30
|
|
|
.An Joachim Wiberg Aq Mt troglobit@gmail.com
|
2019-12-07 17:06:14 +05:30
|
|
|
picked up maintenance. In 2019 the project was revived with fresh DNA
|
2019-12-09 15:33:06 +05:30
|
|
|
strands from both
|
|
|
|
.Fx
|
|
|
|
and
|
|
|
|
.Nx ,
|
2019-12-07 17:06:14 +05:30
|
|
|
.Nm klogd
|
2019-12-09 22:50:28 +05:30
|
|
|
was removed in v2.1 and the project was then re-licensed under the
|
|
|
|
3-clause BSD license, like its brethren.
|
2019-12-09 15:33:06 +05:30
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
utility first appeared in
|
|
|
|
.Bx 4.3 .
|
2019-12-07 15:19:36 +05:30
|
|
|
.Sh BUGS
|
2019-12-09 15:33:06 +05:30
|
|
|
The ability to log messages received in UDP packets is equivalent to an
|
|
|
|
unauthenticated remote disk-filling service, and should probably be
|
|
|
|
disabled
|
|
|
|
.Fl ( s )
|
|
|
|
by default. (The shipped systemd unit file disables this by default.)
|
|
|
|
See also
|
|
|
|
.Sx SECURITY
|
|
|
|
for more information on this. A future version of
|
|
|
|
.Nm
|
|
|
|
may include support for TLS, RFC5425, which includes authentication of
|
|
|
|
both senders and receivers. For now there is the
|
2019-12-07 15:19:36 +05:30
|
|
|
.Fl a
|
2019-12-09 15:33:06 +05:30
|
|
|
option, which is strongly recommended when operating as a remote sink.
|
2019-12-07 15:19:36 +05:30
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fl a
|
|
|
|
matching algorithm does not pretend to be very efficient;
|
|
|
|
use of numeric IP addresses is faster than domain name comparison.
|
|
|
|
Since the allowed peer list is being walked linearly,
|
|
|
|
peer groups where frequent messages are being anticipated
|
|
|
|
from should be put early into the
|
|
|
|
.Fl a
|
|
|
|
list.
|
2019-12-09 15:33:06 +05:30
|
|
|
.Pp
|
|
|
|
As mentioned in the
|
|
|
|
.Sx DESCRIPTION ,
|
|
|
|
.Nm
|
|
|
|
transparently supports the standard C library
|
|
|
|
.Xr syslog 3
|
|
|
|
API. If a binary linked to the standard C libraries does not operate
|
|
|
|
correctly, this should be reported as a bug to the
|
|
|
|
.Lk https://github.com/troglobit/sysklogd/issues sysklogd issue tracker
|