From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: bojohan+news@dd.chalmers.se (Johan Bockgård)
Cc: help-gnu-emacs@gnu.org
Subject: Re: What does code 123 mean?... (Shell command failed with code 123 and no output)
Date: Sat, 7 Jun 2008 12:10:19 +0200 [thread overview]
Message-ID: <1D8665A5-F993-4930-BD93-40CBC907A07C@Web.DE> (raw)
In-Reply-To: <yoij3anpipkb.fsf@remote5.student.chalmers.se>
Am 07.06.2008 um 11:04 schrieb Johan Bockgård:
> EXIT STATUS
> xargs exits with the following status:
> 0 if it succeeds
> 123 if any invocation of the command exited with status 1-125
> 124 if the command exited with status 255
> 125 if the command is killed by a signal
> 126 if the command cannot be run
> 127 if the command is not found
> 1 if some other error occurred.
>
> Exit codes greater than 128 are used by the shell to
> indicate
> that a
> program died due to a fatal signal.
You have a complicated xargs! Look, mine from FreeBSD, only offers:
DIAGNOSTICS
The xargs utility exits with a value of 0 if no error occurs.
If utility
cannot be found, xargs exits with a value of 127, otherwise if
utility
cannot be executed, xargs exits with a value of 126. If any
other error
occurs, xargs exits with a value of 1.
--
Greetings
Pete
Engineer: a mechanism for converting caffeine into designs
next prev parent reply other threads:[~2008-06-07 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12830.1212812278.18990.help-gnu-emacs@gnu.org>
2008-06-07 9:04 ` What does code 123 mean?... (Shell command failed with code 123 and no output) Johan Bockgård
2008-06-07 10:10 ` Peter Dyballa [this message]
2008-06-07 4:16 Don Saklad
[not found] <mailman.12730.1212734180.18990.help-gnu-emacs@gnu.org>
2008-06-06 7:30 ` Xah
2008-06-06 23:45 ` Tim X
-- strict thread matches above, loose matches on Subject: below --
2008-06-06 6:34 Don Saklad
2008-06-06 10:33 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1D8665A5-F993-4930-BD93-40CBC907A07C@Web.DE \
--to=peter_dyballa@web.de \
--cc=bojohan+news@dd.chalmers.se \
--cc=help-gnu-emacs@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).