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/