You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 Regular log messages use year 1969 in timestamp #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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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
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
/var/run/syslogd.cache
, which saves the last seen/logged sequence id read from/dev/kmsg
syslogd(8)
manual page name of the syslogd PID fileThis discussion was created from the release sysklogd v2.2.3.
Beta Was this translation helpful? Give feedback.
All reactions