sysklogd v2.6.0

Changes

• Add reload command for systemd service, by Paweł Jasiak
• Add global log rotation options to .conf file, issue #80. Introducing two new settings: rotate_size SIZE and rotate_count COUNT
• Semantic change for per-file log rotation settings, no longer possible to disable log rotation for a file by setting rotate=0:0
• Possible to set only size or count rotation per file
• Add support for listen addr:port to .conf file, issue #83

Fixes

• Fix #72: loss of raw kernel log messages to console. This adds a new command line flag -l to keep kernel logs to console. A feature requested by embedded Linux users who often navigate issues by console output

  With properly configured kernel logging, e.g., quiet, only error and above in severity is logged by the kernel directly to the console. So for most users this would be a useful behavior

• Fix #81: blocking delay for unresolvable remote log server. If DNS name is used as remote log server, the system may not be able to resolve it to an IP address (for various reasons). This may lead to blocking delays in syslogd causing loss of log messages

• Fix #82: retry creating UNIX and network sockets on failure. This now allows syslogd to "discover" and bind to addresses that are not yet set when it starts up

sysklogd v2.5.2

Minor fix release.

Fixes

• Issue #67: restore support for reading kernel logs from /proc/kmsg,
  regression introduced in v2.4.0, issue #48.

sysklogd v2.5.1

Minor fix release.

Fixes

• Issue #37: improved accuracy of the MARK timer, optional, default: 20
  minutes. Generates log messages to files, which have had no activity
  within the MARK interval. Was off by up to interval / 2 minutes.
  It may now be off by up to 1 / 2 minutes, i.e.g, 30 seconds.
• Issue #64: sub-second faking of kernel timestamps was always zero

sysklogd v2.5.0

Changes

• Issue #59: initial port to NuttX, contributed by Xiaomi
• Issue #61: add support for -c and -cc to disable log compression.
  A single -c disables compression for pipes, another -c (or -cc)
  disables compression for all other log targets
• The default syslog.conf now logs debug messages again (disabled in
  v2.4.0) due to problems (confusion) reported in the field
• Dropped not recommended KillMode=process from systemd unit file

Fixes

• Issue #60: document how to set side-wide permissions on log files
• Issue #62: early log messages lost when running under systemd, found
  by Wind River Systems, including initial fix

sysklogd v2.4.4

Fixes

• Fix #58: running syslogd with -T should use local time for remote
  messages, but time is always logged with "Jan 0 00:00:00".

sysklogd v2.4.3

Changes

• Ensure output from syslogd -v and logger -v is the same, so
  that the project origin is the same, and that both use stdout

Fixes

• Fix #57: garbled tag name in std (RFC3164) log file output

sysklogd v2.4.2

Fixes

• Fix logger default severity, use .notice, like other logger
  implementations. Was .info, which is of lesser severity, affecting
  some use-cases negatively (loss of logs)
• Drop extra leading space in log message in libsyslog RFC3164 format,
  two spaces between proc[pid]:, or plain :, and the message
• Drop trailing space in logger messages read from command line

sysklogd v2.4.1

Changes

• Fake microsecond timestamp to allow for improved log sorting:
  • in RFC3164 messages (that don't have this resolution)
  • in untrusted kernel messages
• Dropped debian/ directory (moved to separate branch), to ease
  re-packaging by downstream
• libsyslog now supports logging to remote servers, bypassing syslogd
• Major updates to logger:
  • Support for logging to a remote host, -h HOST and -P PORT
  • Support for logging in RFC3164 format, -b, mostly for remote
    logging to syslog servers that do not support RFC5424
  • Support for overriding hostname -H NAME
  • Support for custom PID, e.g., a shell scripts PID, -I PID

Fixes

• Fix #52: Prevent over-read when scanning a new-style kernel message.
  Found and fixed by Edward K. McGuire
• Fix #53: prevent log file corruption when kernel messages contain
  control codes, notably \n. Instead, preserve kernel protective
  C-style hex encoding. For example, \n embedded in a message by a
  kernel-level facility is received as \x0a. Found and fixed by
  Edward K. McGuire
• Fix #56: logging to remote machine stops after receiving a few
  SIGHUPs. Open remote socket count was not reset properly on SIGHUP.
  Problem introduced in v2.4.0. Reported by Edward K. McGuire
• Fix gettimeofday() error handling to use same fallback to time()
• Fix libsyslog opening and connecting to syslogd when LOG_NLOG is set
• Fix libsyslog so it honors LOG_PTRIM when logging to stderr
• Fix issue in RFC3164 output where the tag field could overflow.
  Spec. mandates tag never exceeds 32 characters

sysklogd v2.4.0

Changes

• Add support for secure_mode=[0,1,2] to syslog.conf, same as -s but easier to use and activate with SIGHUP
• Enable secure_mode=1 (only log to remote servers) in default syslog.conf
• Disable debug messages, in default syslog.conf, from /var/log/syslog
• Rename option -K to -t for trusting kernel timestamp, issue #42
• Add option -K to disable kernel logging, issue #48
• Rudimentary support for detecting if running in a container and then disable kernel logging automatically, issue #48
• Add support for notify PATH option to syslog.conf, for calling an external script on log rotation, by Steffen Nurpmeso, issue #45
• Add support for log rotation on SIGUSR2, by Steffen Nurpmeso, issue #46
• Update manual page for -b option description

Fixes

• Issue #41: add missing -H option to usage text
• Issue #44: option misspelled in man page
• Issue #47: do not lose file mode on rotated files, by Steffen Nurpmeso
• Issue #48: verify kernel log FIFO is a proper character device, for running in certain container setups
• Issue #49: add support for -8 command line option to allow 8-bit data to be logged -- this is a temporary fix until we have support for parsing the Unicode BOM, as defined in RFC5424
• Issue #50: fix issue with wall message, by Edward K. McGuire

sysklogd v2.3.0

Changes

• Add support for logger -k, early log to /dev/kmsg. Useful when
  logging from early system startup scripts before syslogd has started
• Support for extracting non-kernel log messages from /dev/kmsg
• Ignore EINVAL from kernel, caused warning message at first startup
• Use journald socket on systemd systems, not /dev/log
• Issue #38: add support for syslogd -C file to use file for caching
  the last seen kernel sequence number, default: /run/syslogd.cache.
  Note: syslogd relies on the location of this file to be wiped at
  system boot. The default, /run, is a RAM disk on modern systems

Fixes

• Issue #34: regression in v2.2.3, causing loss of syslogd log messages
  like syslogd v2.2.3: restart.
• Issue #35: man pages lists -v as verbose mode, is actually version
• Issue #36: retry DNS lookup of remote syslog servers with res_init()
  to ensure name resolution at bootup when a remote DNS may temporarily
  be unreachable. Retry at most every five seconds, to prevent syslogd
  from monopolizing the CPU when emptying the kernel ring buffer
• Issue #39: update tests to use -P fn and -C fn
• Issue #40: improve documentation for syslogd.cache file requirements
• Issue #41: add missing documentation for -H option
• Issue #42: add option (-K) to always trust kernel timestamp. By
  default syslogd only trusts the kernel timestamp for the initial
  emptying of the kernel ring buffer
• Issue #43: avoid asserting (exiting) on and around Jan 19, 2038, when
  the UNIX epoch wraps around on 32-bit time_t systems
• libsyslog: handle EOVERFLOW from gettimeofday() on Jan 19, 2038
• Avoid NULL pointers to internal logit() function, only triggered
  when in debug mode
• Replace \m with \n (missing newline) in logger usage text

Packages for Debian 10, or later, and compatible Ubuntu releases, available at https://deb.troglobit.com/