diff options
author | Csaba Henk <csaba@redhat.com> | 2012-04-24 11:53:56 +0200 |
---|---|---|
committer | Anand Avati <avati@redhat.com> | 2012-06-01 16:49:39 -0700 |
commit | 2084c0e3d748b7e28d2fc9749ad9d1e2bf63208c (patch) | |
tree | 0137bf6ad134ed2d81aaa1c2c9fc3cc046b3d24e /glusterfs-hadoop | |
parent | 982be4925851e13b027c5dce59e7a92a76cb9aae (diff) |
cli: let commands specify the exit value in batch mode
Old behavior: when cli is ran in batch mode (sequence of commands are
fed to it in stdin), if a command returns an error (ie. -1), the cli
exits upon it with 255 (-1 on 8 bit).
New behavior: consider any non-zero return from cli commands as error
and use the negative of that return value as exit value, thus giving
control to cli commands over the exit value, while (as of the existing
command set) adhering to the convention of exiting with 1 on error.
Spotted upon stumbling upon mount/umount commands which did want
to exit with 1 on error but that was not possible as of old behavior.
Change-Id: I6f41191cdc718c3e676cfae1e404152f4cb715c5
BUG: 765214
Signed-off-by: Csaba Henk <csaba@redhat.com>
Reviewed-on: http://review.gluster.com/3218
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Amar Tumballi <amarts@redhat.com>
Reviewed-by: Anand Avati <avati@redhat.com>
Diffstat (limited to 'glusterfs-hadoop')
0 files changed, 0 insertions, 0 deletions