Public bug reported: As per the issue created on syslog-ng's GitHub repository: https://github.com/balabit/syslog-ng/issues/1098
When content is piped to `logger`, every message gets the timestamp of when the logger process started. This is a regression between 14.04 and 16.04. Previously, logger would report an individual timestamp per message. A workaround is to let syslog create the timestamp rather than logger. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1596723 Title: logger(1) continuously outputs same timestamp Status in util-linux package in Ubuntu: New Bug description: As per the issue created on syslog-ng's GitHub repository: https://github.com/balabit/syslog-ng/issues/1098 When content is piped to `logger`, every message gets the timestamp of when the logger process started. This is a regression between 14.04 and 16.04. Previously, logger would report an individual timestamp per message. A workaround is to let syslog create the timestamp rather than logger. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1596723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp