Package: bsdutils Version: 1:2.38.1-4 Severity: normal X-Debbugs-Cc: t...@mirbsd.de
I *know* we had this bug already, and it got fixed at some time, but apparently a regression was introduced and this bug shows up again in sid: long-running logger(1) sessions do not receive an updated timestamp for later lines: root@ara4:~ # tail -F /var/log/syslog& root@ara4:~ # (echo foo; sleep 5; echo bar) | logger -t baz Feb 2 02:04:24 ara4 baz: foo Feb 2 02:04:24 ara4 baz: bar Compare bullseye: tglase@x61w:~ $ (echo foo; sleep 5; echo bar) | logger -t baz Feb 2 03:04:45 x61w baz: foo Feb 2 03:04:50 x61w baz: bar I use “dæmonprogram | logger -t nameofthat” quite often, and having output with ancient timestamps suddenly show up in logs is confusing (especially fail2ban very much dislikes that). For the sake of completeness, the bullseye system uses inetutils-syslogd 2:2.0-1+deb11u1, the sid system has inetutils-syslogd 2:2.4-2, but TTBOMK the timestamp is generated by logger(1), not the syslog dæmon (that would be weird). -- System Information: Debian Release: bookworm/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: m68k Kernel: Linux 6.1.0-2-m68k (UP) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: sysvinit (via /sbin/init) Versions of packages bsdutils depends on: ii libc6 2.36-4+ports ii libsystemd0 252.4-1 Versions of packages bsdutils recommends: ii bsdextrautils 2.38.1-4 bsdutils suggests no packages. -- no debconf information
