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 stats. >> >> Thanks for the report, but that behavior is required by POSIX. >> dd must handle SIGINT the way you want, but dd may not handle >> SIGPIPE that way: >> >> ASYNCHRONOUS EVENTS >> >> For SIGINT, the dd utility shall interrupt its current processing, >> write status information to standard error, and exit as though >> terminated by SIGINT. It shall take the standard action for all >> other signals; see the ASYNCHRONOUS EVENTS section in Section 1.4 >> (on page 2280). > > Please interpret it as dd is supposed to work: > > Please block the "SIGPIPE" signal, then write will return: ... > If you start "waving standards around", I'll bounce it back for you.
You're beating a dead horse already. 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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
