From: Vadim Kochan <vadim4j@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [PATCH 1/4] ip: document exit code
Date: Wed, 6 May 2015 20:16:25 +0300 [thread overview]
Message-ID: <20150506171625.GA849@angus-think.lan> (raw)
In-Reply-To: <1430931483-28595-2-git-send-email-stephen@networkplumber.org>
Hi,
On Wed, May 06, 2015 at 09:58:00AM -0700, Stephen Hemminger wrote:
> From: Stephen Hemminger <shemming@brocade.com>
>
> The ip command has always had a consistent exit status
> document it so that developers see it.
> ---
> man/man8/ip.8 | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/man/man8/ip.8 b/man/man8/ip.8
> index 43ddac9..9574a50 100644
> --- a/man/man8/ip.8
> +++ b/man/man8/ip.8
> @@ -275,6 +275,10 @@ Usually it is
> or, if the objects of this class cannot be listed,
> .BR "help" .
>
> +.SH EXIT STATUS
> +Exit statsis is 0 if command was sucessful, and 1 if there is a syntax error.
statsis -> status ? sucessful -> successful ?
> +If an error was reported by the kernel exit status is 2.
> +
> .SH HISTORY
> .B ip
> was written by Alexey N. Kuznetsov and added in Linux 2.2.
> --
> 2.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-06 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 16:57 [PATCH 0/4] iproute2: exit code fixes Stephen Hemminger
2015-05-06 16:58 ` [PATCH 1/4] ip: document exit code Stephen Hemminger
2015-05-06 17:16 ` Vadim Kochan [this message]
2015-05-06 16:58 ` [PATCH 2/4] ip: return correct exit code on route failure Stephen Hemminger
2015-05-06 17:19 ` roopa
2015-05-06 17:25 ` Vadim Kochan
2015-05-06 16:58 ` [PATCH 3/4] ip: fix exit code for rule failures Stephen Hemminger
2015-05-06 16:58 ` [PATCH 4/4] ip: fix exit code for addrlabel Stephen Hemminger
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=20150506171625.GA849@angus-think.lan \
--to=vadim4j@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemming@brocade.com \
--cc=stephen@networkplumber.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 NNTP newsgroup(s).