Date: Wed, 07 Jan 2009 01:13:54 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Hiroki Sato <hrs@FreeBSD.org> Cc: danger@FreeBSD.org, doc@FreeBSD.org Subject: Re: svn commit: r186737 - head/sbin/geom/class/virstor Message-ID: <87vdssqb7x.fsf@kobe.laptop> In-Reply-To: <20090105.054435.125149473.hrs@allbsd.org> (Hiroki Sato's message of "Mon, 05 Jan 2009 05:44:35 %2B0900 (JST)") References: <1289663263.20090104185721@rulez.sk> <20090105.032211.33865530.hrs@allbsd.org> <20090104194844.GB1257@haakonia.hitnet.RWTH-Aachen.DE> <20090105.054435.125149473.hrs@allbsd.org>
index | next in thread | previous in thread | raw e-mail
On Mon, 05 Jan 2009 05:44:35 +0900 (JST), Hiroki Sato <hrs@FreeBSD.org> wrote:
> 2. Otherwise, EXIT STATUS section should match the reality as
> possible. This means if a command returns 0 on success, 1 on
> error, and the other values are not returned, the description in
> the manual page should be "it exits 0 on success, and 1 if an
> error occurs".
Agreed. There are tools that assign special meanings to separate >0
error codes, i.e. diff3(1) which exits with:
0 when successful
1 when there are conflicts in the three files being merged
2 when something unexpected but bad nonetheless happens
Being precise about the error codes is critical in this case. It may be
equally important in other places too.
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87vdssqb7x.fsf>