Hi Zbyszek,
On 30.10.2014 22:42, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Oct 30, 2014 at 06:49:32PM +0100, Andreas Cadhalpun wrote:
The fix for this would be for journald to correctly interpret the
carriage return. Therefore I'm reassigning this bug to systemd.
Nope, there's no place for '\r' in logs.
Yes, '\r' (or '#015') should not end up in the logs.
It only makes sense on
a console, where you show something and then erase it some time
later when the situation changes.
freshclam can also be run from the console, where it shows the progress
in real time on stdout.
Log file viewers don't show
logs in real time, so any usage of erase characters should be
replaced by simply logging the final version in the first place.
Systemd/journald just captures stdout, which is originally meant for a
console. So I think it should handle '\r' more gracefully, by simply
only including the final version in the log.
Or how do you think this should be solved?
Best regards,
Andreas
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
