On Saturday 04 August 2007 15:45:56 Loïc Grenié wrote:
> 2007/8/4, Alexander Kriegisch <[EMAIL PROTECTED]>:
> > I would like to determine the exit code of 'foo' in
> > foo | bar
> >
> > I bash there is the PIPESTATUS array, but in ash (which I must use)
> > there is no such thing as PIPESTATUS or a
> x=`((( foo 3>&- 4>&- ); echo $? >&3)| bar >&4 3>&- 4>&-) 3>&1` 4>&1
Thanks, Loïc. I will consider your solution if I ever have a case like
this again, but my current workaround is rather simple to read and uses
a text buffer for the first command's output. I can do this because I
know that foo'
2007/8/4, Alexander Kriegisch <[EMAIL PROTECTED]>:
> I would like to determine the exit code of 'foo' in
> foo | bar
>
> I bash there is the PIPESTATUS array, but in ash (which I must use)
> there is no such thing as PIPESTATUS or arrays. Is there any canonical
> way or at least a workaround to ach
On Saturday 04 August 2007, Cristian Ionescu-Idbohrn wrote:
> ...which is the latest distributed.
no it isnt, Debian is out of date
> CC miscutils/readahead.o
> CC miscutils/taskset.o
if the applets fail, dont enable them
-mike
signature.asc
Description: This is a digitally signe
I would like to determine the exit code of 'foo' in
foo | bar
I bash there is the PIPESTATUS array, but in ash (which I must use)
there is no such thing as PIPESTATUS or arrays. Is there any canonical
way or at least a workaround to achieve both piping the foo's output
into bar unconditionally *an
...which is the latest distributed.
CC miscutils/readahead.o
miscutils/readahead.c: In function `readahead_main':
miscutils/readahead.c:27: warning: implicit declaration of function `readahead'
CC miscutils/taskset.o
miscutils/taskset.c:17: error: syntax error before '*' token
misc
Please find attached a sorted list of "declared with attribute
warn_unused_result" warnings.
Cheers,
--
Cristianinit/init.c:923:warning: ignoring return value
of 'chdir', declared with attribute warn_unused_result
procps/fuser.c:278:
