Your message dated Sun, 3 May 2020 22:27:15 +0200
with message-id <[email protected]>
and subject line Re: Bug#630855: [bsdutils] script: please offer recording
timing information in output file
has caused the Debian Bug report #630855,
regarding [bsdutils] script: please offer recording timing information in
output file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
630855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630855
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bsdutils
Version: 1:2.19.1-1
Severity: wishlist
Tags: upstream
script offers -t to record timing information on stderr. This is great,
but it would be convenient to have another mode offering to prefix each
output [line] with a timestamp (or how much time elapsed since the
previous output). My idea would be to record the debugging info / errors
from running a KDE application, which outputs one message per line. I
did that with moreutils's ts instead.
--- End Message ---
--- Begin Message ---
Version: 2.35.1-1
* Filipus Klutiero <[email protected]> [200503 20:26]:
> script offers -t to record timing information on stderr. This is great, but
> it would be convenient to have another mode offering to prefix each output
> [line] with a timestamp (or how much time elapsed since the previous
> output). My idea would be to record the debugging info / errors from running
> a KDE application, which outputs one message per line. I did that with
> moreutils's ts instead.
I belive upstream has implemented improved timing/logging in 2.35.
Thanks,
Chris
--- End Message ---
