From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <138575260908180741j56414d5dxcfa1fbc30a48bb3d@mail.gmail.com> References: <138575260908180741j56414d5dxcfa1fbc30a48bb3d@mail.gmail.com> Date: Tue, 18 Aug 2009 16:55:59 +0200 Message-ID: <5d375e920908180755v50f628b2h2cc823af67e37c8@mail.gmail.com> From: Uriel To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] sed oddity Topicbox-Message-UUID: 4da9740c-ead5-11e9-9d60-3106f5b1d025 Interesting, this reminds me of a question I had: is there any command that would read from stdin, and write to stdout, but if there was an error when writing to stdout it would ignore it and continue reading stdin? It is trivial to do it in C, but don't want to require an extra program just to keep werc's error logs clean of spurious noise. I guess based on what you said, that I might be able to use sed, but only until your complaint is fixed :) uriel On Tue, Aug 18, 2009 at 4:41 PM, hugo rivera wrote: > Hi, > is there some reason why sed doesn't check for write errors on its > stdout? (or at least it doesn't report them) > I am implementing a fs, and I wasted my whole afternoon trying to figure out why > sed 300q file > mnt/data > doesn't say anything about the write error I was expecting. > Note that > sed 300q file | cat > mnt/data > shows my error message ;-) > Am I missing something? > Saludos > > -- > Hugo > >