[Syslog-ng-maintainers] Bug#802888: syslog-ng: Fixed in syslog-ng 3.7.3
jmomo at jmomo.net
Sat Mar 19 07:12:16 GMT 2016
Followup-For: Bug #802888
I was finding this bug today on my system. Noticed that all of my kernel messages were from five minutes in the future.
It looks like this bug has finally been fixed as of last month:
Looks like it's supposed to be fixed in 3.7.3. 3.7.1 is is unstable as I write this, so this bug should be toast soon.
This has been a known issue for more than two years now??? Wow.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages syslog-ng depends on:
ii syslog-ng-core 3.5.6-2.1+b1
ii syslog-ng-mod-json 3.5.6-2.1+b1
ii syslog-ng-mod-mongodb 3.5.6-2.1+b1
ii syslog-ng-mod-sql 3.5.6-2.1+b1
Versions of packages syslog-ng recommends:
ii syslog-ng-mod-amqp 3.5.6-2.1+b1
ii syslog-ng-mod-geoip 3.5.6-2.1+b1
ii syslog-ng-mod-redis 3.5.6-2.1+b1
ii syslog-ng-mod-smtp 3.5.6-2.1+b1
ii syslog-ng-mod-stomp 3.5.6-2.1+b1
syslog-ng suggests no packages.
-- no debconf information
More information about the Syslog-ng-maintainers