you don't really want to get "write error" printed from every
process in a pipe line such as
slowly-compute-big-file | dosomemore | andyetmore | sed -n
'/something/;p;q'
or even
slowly-compute-big-file | badusageofsomething
where the latter prints a "usage" message and quits.
you want to make sure the previous commands in the pipeline stop, right away.
(they might be in a script. they might even be costing money.)
actually, if i were looking for something exceptional to fix,
i'd get linux and the BSDs to stop thinking they still
need character and block "special files" as special
types of files in a physical file system, to represent devices.
--- Begin Message ---
On Jul 19, 2009, at 2:55 PM, Charles Forsyth wrote:
not for network connections?
i think pipe is the only case, and even that is suppressed
for pipes that carry 9p, after mounting.
one last kick of a dead horse: see that's exactly what I'm
talking about -- all these exceptions and for what? I'm
pretty sure if we change the devpipe today not to send
a note nobody would even notice...
Thanks,
Roman.
--- End Message ---
