[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Detecting errors in a pipe in ash
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2009-12-05 14:13:36
Message-ID: 200912051513.36621.vda.linux () googlemail ! com
[Download RAW message or body]

On Saturday 05 December 2009 09:48, Michael Abbott wrote:
> On Fri, 4 Dec 2009, Denys Vlasenko wrote:
> > On Friday 04 December 2009 12:37, Michael Abbott wrote:
> > > Well, looking more closely at ash it's clear that the only solution is 
> > > to implement this function.  Fortunately (unless I've missed 
> > > something, likely enough, there's a lot of code there) it seems easier 
> > > than I feared:
> > 
> > Applied, thanks!
> > 
> > I edited it a bit and made conditional on ASH_BASH_COMPAT.
> 
> Thanks for applying that.  Just one remark:
> 
> Are you sure that 
> 	status == 0
> is an adequate replacement for
> 	WIFEXITED(status) && WEXITSTATUS(status) == 0
> ?  The man page for wait(2) only tells us about using these macros, so do 
> there exist implementations of wait() which return their status 
> differently? 

I think even other Unixes like BSD use the same status word layout.
--
vda
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]