sysklogd v2.6.2

Changes

• syslog.conf: misplaced continuation character in example
• Adapt facilities for RFC5424 compliance. Add aliases for the standard
  LOG_CRON2 and LOG_AUDIT, including facilitynames[], issue #86
• Add support for IPv6 addresses in listen directive, issue #90

Fixes

• Fix #85: logging to remote IPv6 address does not work. Add support
  for parsing [fdd5::6979:c0ff:ee87:8f92]:123 style addresses
• Fix #88: initial delay for unresolvable remote target. When a DNS
  name cannot be resolved, e.g., critically at boot, syslogd was
  blocked with default resolver timeout (5 * 2 sec)
• Fix #89: data corruption using the listen directive in .conf files

sysklogd v2.6.1

Changes

• Read .conf files from include directories sorted alphabetically

Fixes

• Add extra linefeed to wall messages to ensure they are seen
• Issue #87: segfault on SIGTERM, regression from v2.6.0

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