Control: tags -1 upstream wontfix
Control: found -1 2.29.2-1+deb9u1

* Thorsten Glaser <t...@mirbsd.de> [230202 03:21]:
> 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:

This is a design decision of upstream, introduced in 2015 (so,
before buster):

logger.c line 964ff:

        /* note: we never re-generate the syslog header here, even if we
         * generate multiple messages. If so, we think it is the right thing
         * to do to report them with the same timestamp, as the user actually
         * intended to send a single message.
         */

https://github.com/util-linux/util-linux/commit/2b3f40c5978569f15e30836cf99f34f31c163d1c#diff-288c0fc14bc650526985c9f780a50739c397d1c5ca39aa1046b224e9efd3d619R519
(by Rainer Gerhards, aka rsyslog developer)

Good luck,
Chris

Reply via email to