GNU bug report logs - #12489
inconsistent output from 'dd' w/rt stats and suppression.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Pádraig Brady <P <at> draigBrady.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#12489: closed (inconsistent output from 'dd' w/rt stats and
 suppression.)
Date: Mon, 24 Sep 2012 02:50:04 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 24 Sep 2012 03:47:25 +0100
with message-id <505FC9BD.1010002 <at> draigBrady.com>
and subject line Re: bug#12489: inconsistent output from 'dd' w/rt stats and suppression.
has caused the debbugs.gnu.org bug report #12489,
regarding inconsistent output from 'dd' w/rt stats and suppression.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
12489: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12489
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Linda Walsh <coreutils <at> tlinx.org>
To: bug-coreutils <at> gnu.org
Subject: inconsistent output from 'dd' w/rt stats and suppression.
Date: Sat, 22 Sep 2012 12:09:55 -0700

If I have 'dd' running, and want to see stats, the manpage says I can 
send it
a USR1 signal and it will print "I/O statistics to standard error and 
then resume copying".  I see something like:
          18335302+0  records  in  18335302+0 records out 9387674624 bytes
             (9.4 GB) copied, 34.6279 seconds, 271 MB/s

The same I/O statistics are displayed at the end of a 'dd' session:

18335302+0 records  in
18335302+0 records out
9387674624 bytes (9.4 GB) copied, 34.6279 seconds, 271 MB/s

The man page says I can use the
"status=noxfer" to suppress transfer statistics".

But when I use it the number of records transfered into 'dd'
and out of 'dd' are still displayed.  Suppressed is the
sum of the bytes transferred in and out, and the time+rate.

So... it seems status=noxfer isn't fully suppressing the statistics
but more accurately only suppresses the summary, time and rate
stats and not the # records transfered in and out.

Either way... shouldn't it just suppress the whole message,
or what's the point?  What switch would one use to suppress
all I/O statistics?

Thanks,
Linda

[Message part 3 (message/rfc822, inline)]

From: Pádraig Brady <P <at> draigBrady.com>
To: pozsy <at> uhulinux.hu
Cc: 12489-done <at> debbugs.gnu.org, Linda Walsh <coreutils <at> tlinx.org>
Subject: Re: bug#12489: inconsistent output from 'dd' w/rt stats and
	suppression.
Date: Mon, 24 Sep 2012 03:47:25 +0100

[Message part 4 (text/plain, inline)]

On 09/23/2012 12:12 PM, Pádraig Brady wrote:
> I think there was general consensus that the status=noinfo should be applied
> http://lists.gnu.org/archive/html/bug-coreutils/2010-02/msg00159.html
>
> I'll look at that this evening.

I changed things a bit in the attached patch.
I used 'status=none' rather than 'status=noinfo',
to make it obvious all stderr messages were being suppressed.
Also, I kept the bitmask nature of the existing code
to make it more consistent and extendible.

cheers,
Pádraig.

[dd-status-none.diff (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.