From: John Adams <johna@onevista.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Need blocking /dev/null
Date: Fri, 2 Nov 2001 16:04:13 -0400 [thread overview]
Message-ID: <01110215041301.01066@flash> (raw)
In-Reply-To: <Pine.LNX.4.21.0111012322310.14742-100000@Consulate.UFP.CX>
In-Reply-To: <Pine.LNX.4.21.0111012322310.14742-100000@Consulate.UFP.CX>
On Thursday 01 November 2001 18:51, Riley Williams wrote:
> Hi Doug.
>
> >> Are you sure?
> >>
> >>> find / -name "wanted-but-lost-download" | eat
> >>
> >> Doesn't work - you're piping the stdin there, not stderr as per my
> >> example above. AFAIK, there's no way to pipe stderr without also
> >> piping stdout, hence this sort of solution just doesn't work.
> >
> > The Bourne shell is more perverse than you realize:
> >
> > $ exec 3>&1; find / -name "wanted-but-lost-download" 2>&1 1>&3 3>&- |
> > eat
> >
> > [stolen from "Csh Programming Considered Harmful" by Tom Christiansen]
> >
> > Horrible, but does work. ;)
You really do take the hard way. Try this to pipe just stderr:
command_that_outputs_on_1_and_2 2>/dev/stdout 1>/dev/null | eat
next prev parent reply other threads:[~2001-11-02 20:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 21:07 Need blocking /dev/null Marko Rauhamaa
2001-10-29 21:24 ` Alan Cox
2001-10-30 3:52 ` Marko Rauhamaa
2001-10-30 7:02 ` Tim Connors
2001-10-30 16:04 ` Marko Rauhamaa
2001-10-31 0:51 ` Riley Williams
2001-10-31 9:23 ` Ville Herva
2001-10-31 23:13 ` Riley Williams
2001-11-01 0:11 ` Doug McNaught
2001-11-01 7:27 ` Ville Herva
2001-11-01 7:52 ` Abramo Bagnara
2001-11-01 23:51 ` Riley Williams
2001-11-02 19:53 ` Ville Herva
2001-11-02 20:04 ` John Adams [this message]
2001-11-02 20:32 ` Ville Herva
2001-11-02 20:46 ` Tim Walberg
2001-11-05 22:08 ` Andreas Schwab
2001-11-01 7:24 ` Ville Herva
2001-10-29 21:45 ` Hugh Dickins
2001-10-29 23:03 ` elko
2001-10-29 23:12 ` Mike Fedyk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01110215041301.01066@flash \
--to=johna@onevista.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.