On Mon, Jan 28, 2008 at 10:50:23PM -0700, Bob Proulx wrote:
Michael Stone wrote:
Rogier Wolff wrote:
dd if=somebigfile | dd count=100 of=/dev/null
both dd's should report that they copied 100 records. This worked in
debian sarge. Debian Etch, the first dd stopped reporting the
On Tue, Jan 29, 2008 at 03:12:24PM +0100, Jim Meyering wrote:
Rogier Wolff [EMAIL PROTECTED] wrote:
On Tue, Jan 29, 2008 at 08:01:45AM -0500, Michael Stone wrote:
I figured there'd be some piece of posix at the bottom of it. :) I
wonder if the documentation should better reflect that. (The
Rogier Wolff [EMAIL PROTECTED] wrote:
+and when @command{dd} completes normally or is killed by the
[EMAIL PROTECTED] signal, it outputs the final statistics.
Which is not correct, as the stats are also printed upon write error,
like ENOSPC. (as we all agree the standards require).
It
$ dd if=/dev/zero | dd count=100 of=/dev/null
Of course, the two dd's are unneccesary, and this could be done with
one dd. In practise, the consumer (second dd) is another program that
exits when it's had enough data. The output of (the first) dd is then
used to extract the approximate
Rogier Wolff [EMAIL PROTECTED] wrote:
On Tue, Jan 29, 2008 at 01:27:57PM +0100, Jim Meyering wrote:
Rogier Wolff [EMAIL PROTECTED] wrote:
...
Let me reiterate: It is the first dd that is misbehaving, when it
recieves a write error and SIGPIPE, it simply exits instead of
reporting the
Rogier Wolff [EMAIL PROTECTED] wrote:
On Tue, Jan 29, 2008 at 08:01:45AM -0500, Michael Stone wrote:
I figured there'd be some piece of posix at the bottom of it. :) I
wonder if the documentation should better reflect that. (The info page
says only that when dd completes it outputs the final
+and when @command{dd} completes normally or is killed by the
[EMAIL PROTECTED] signal, it outputs the final statistics.
Which is not correct, as the stats are also printed upon write error,
like ENOSPC. (as we all agree the standards require).
Roger.
--
** [EMAIL PROTECTED] **
Michael Stone [EMAIL PROTECTED] wrote:
On Tue, Jan 29, 2008 at 01:27:57PM +0100, Jim Meyering wrote:
Rogier Wolff [EMAIL PROTECTED] wrote:
...
Let me reiterate: It is the first dd that is misbehaving, when it
recieves a write error and SIGPIPE, it simply exits instead of
reporting the stats.
On Tue, Jan 29, 2008 at 08:01:45AM -0500, Michael Stone wrote:
I figured there'd be some piece of posix at the bottom of it. :) I
wonder if the documentation should better reflect that. (The info page
says only that when dd completes it outputs the final statistics; maybe
something like
On Tue, Jan 29, 2008 at 01:27:57PM +0100, Jim Meyering wrote:
Rogier Wolff [EMAIL PROTECTED] wrote:
...
Let me reiterate: It is the first dd that is misbehaving, when it
recieves a write error and SIGPIPE, it simply exits instead of
reporting the stats.
Thanks for the report, but that
On Tue, Jan 29, 2008 at 01:27:57PM +0100, Jim Meyering wrote:
Rogier Wolff [EMAIL PROTECTED] wrote:
...
Let me reiterate: It is the first dd that is misbehaving, when it
recieves a write error and SIGPIPE, it simply exits instead of
reporting the stats.
Thanks for the report, but that
Rogier Wolff [EMAIL PROTECTED] wrote:
...
Let me reiterate: It is the first dd that is misbehaving, when it
recieves a write error and SIGPIPE, it simply exits instead of
reporting the stats.
Thanks for the report, but that behavior is required by POSIX.
dd must handle SIGINT the way you want,
On Tue, Jan 29, 2008 at 03:33:01PM +0100, Jim Meyering wrote:
Rogier Wolff [EMAIL PROTECTED] wrote:
On Tue, Jan 29, 2008 at 01:27:57PM +0100, Jim Meyering wrote:
Rogier Wolff [EMAIL PROTECTED] wrote:
...
Let me reiterate: It is the first dd that is misbehaving, when it
recieves a
Rogier Wolff [EMAIL PROTECTED] wrote:
You'll need to come up with much better arguments (that probably
do not exist) to make me change dd to be non-compliant in this respect.
In my interpretation of the quoted part of the standard, dd has become
non-compliant, by not reporting the statistics
Michael Stone wrote:
Rogier Wolff wrote:
dd if=somebigfile | dd count=100 of=/dev/null
both dd's should report that they copied 100 records. This worked in
debian sarge. Debian Etch, the first dd stopped reporting the number
of records copied. The script I wrote then stopped
On Wed, Jan 16, 2008 at 11:26:05AM +0100, Rogier Wolff wrote:
dd if=somebigfile | dd count=100 of=/dev/null
both dd's should report that they copied 100 records. This worked in
debian sarge. Debian Etch, the first dd stopped reporting the number
of records copied. The script I wrote
Package: coreutils
Version: 5.97-5.3
Severity: normal
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22bm
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
17 matches
Mail list logo
