Update changelogs and bump version for v2.2.3 release
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
This commit is contained in:
parent
4accbafa17
commit
17b68ca89a
12
ChangeLog.md
12
ChangeLog.md
@ -4,17 +4,21 @@ Change Log
|
||||
All relevant changes to the project are documented in this file.
|
||||
|
||||
|
||||
[v2.2.3][UNRELEASED]
|
||||
[v2.2.3][] - 2021-05-11
|
||||
-----------------------
|
||||
|
||||
Bug fix release.
|
||||
Bug fix release. The focus is still on tackling the fallout resulting
|
||||
in migrating from the old kernel log interface in `/proc/kmsg` to
|
||||
`/dev/kmsg`, introduced in v2.2.0.
|
||||
|
||||
### Fixes
|
||||
- Issue #28: log messages stuck in 1969. When not using libsyslog, or
|
||||
the bundled logger, the `syslog()` API in the C library is used, which
|
||||
may not necessarily set the timestamp. When sysklogd infers timestamp
|
||||
it was offset by the number of years since 1969, i.e., `boot_time`
|
||||
- Issue #29: kernel messages repeated if syslogd is restarted at runtime
|
||||
- Issue #29: kernel messages repeated if syslogd is restarted at runtime.
|
||||
This introduces a new state file, `/var/run/syslogd.cache`, which
|
||||
saves the last seen/logged sequence id read from `/dev/kmsg`
|
||||
- Issue #31: log message time calculation issue on 32-bit systems
|
||||
- Issue #32: remote kernel messages being mapped to uucp instead of user
|
||||
- Fix `syslogd(8)` manual page name of the syslogd PID file
|
||||
@ -391,7 +395,7 @@ and a replacement for `syslog.h` to enable new features in RFC5424.
|
||||
- Several bugfixes and improvements, please refer to the .c files
|
||||
|
||||
|
||||
[UNRELEASED]: https://github.com/troglobit/sysklogd/compare/v2.2.2...HEAD
|
||||
[UNRELEASED]: https://github.com/troglobit/sysklogd/compare/v2.2.3...HEAD
|
||||
[v2.2.3]: https://github.com/troglobit/sysklogd/compare/v2.2.2...v2.2.3
|
||||
[v2.2.2]: https://github.com/troglobit/sysklogd/compare/v2.2.1...v2.2.2
|
||||
[v2.2.1]: https://github.com/troglobit/sysklogd/compare/v2.2.0...v2.2.1
|
||||
|
@ -25,7 +25,7 @@
|
||||
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
# SUCH DAMAGE.
|
||||
|
||||
AC_INIT([sysklogd], [2.2.3-rc1], [https://github.com/troglobit/sysklogd/issues],,
|
||||
AC_INIT([sysklogd], [2.2.3], [https://github.com/troglobit/sysklogd/issues],,
|
||||
[https://github.com/troglobit/sysklogd])
|
||||
AC_CONFIG_AUX_DIR(aux)
|
||||
AM_INIT_AUTOMAKE([1.11 foreign subdir-objects])
|
||||
|
8
debian/changelog
vendored
8
debian/changelog
vendored
@ -4,12 +4,14 @@ sysklogd (2.2.3) stable; urgency=medium
|
||||
or the bundled logger, the syslog() API in the C library is used, which
|
||||
may not necessarily set the timestamp. When sysklogd infers timestamp
|
||||
it was offset by the number of years since 1969, i.e., boot_time.
|
||||
* Fix problem with repeating kernel messages if syslogd is restarted
|
||||
* Fix problem with repeating kernel messages if syslogd is restarted.
|
||||
This introduces a new state file, /var/run/syslogd.cache, which saves
|
||||
the last seen/logged sequence id read from `/dev/kmsg`
|
||||
* Fix log message time calculation issue on 32-bit systems.
|
||||
* Fix remote kernel messages being mapped to uucp instead of user
|
||||
* Fix syslogd(8) name of PID file (syslog.pid -> syslogd.pid)
|
||||
* Fix man page syslogd(8), name of PID file (syslog.pid -> syslogd.pid)
|
||||
|
||||
-- Joachim Wiberg <troglobit@gmail.com> Wed, 05 May 2021 03:36:37 +0200
|
||||
-- Joachim Wiberg <troglobit@gmail.com> Tue, 11 May 2021 11:20:25 +0200
|
||||
|
||||
sysklogd (2.2.2) stable; urgency=low
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user