On Fri, Oct 24, 2003 at 10:47:22PM +0200, Oleg Goldshmidt wrote:
> Shlomi Fish <[EMAIL PROTECTED]> writes:
>
> > On Fri, 24 Oct 2003, Beni Cherniavsky wrote:
> >
> > > Shlomi Fish wrote on 2003-10-12:
> > >
> > > > I want that if one of the (first) components of the pipeline exits with an
> > > >
Shlomi Fish <[EMAIL PROTECTED]> writes:
> On Fri, 24 Oct 2003, Beni Cherniavsky wrote:
>
> > Shlomi Fish wrote on 2003-10-12:
> >
> > > I want that if one of the (first) components of the pipeline exits with an
> > > error code, I'll know about it somehow. How?
> > >
> > info bash --index PIPESTA
Peace, Linux lovers!
I'm hereby offering to give free/open lectures/series/courses on
a variety
of topics... with the proviso that the community (that's you!)
help make
this have an impact on Linux/FLOSS adoption locally. Right?!
I'm a professional, avid lecturer, with years of experience in
the
On Fri, 24 Oct 2003, Beni Cherniavsky wrote:
> Shlomi Fish wrote on 2003-10-12:
>
> > I want that if one of the (first) components of the pipeline exits with an
> > error code, I'll know about it somehow. How?
> >
> info bash --index PIPESTATUS
>
Cool thanks.
> $ true | false | true | false; ech
Shlomi Fish wrote on 2003-10-12:
> I want that if one of the (first) components of the pipeline exits with an
> error code, I'll know about it somehow. How?
>
info bash --index PIPESTATUS
$ true | false | true | false; echo [EMAIL PROTECTED]
0 1 0 1
$ { true | false | true | false; }; echo [EMAIL
