From d54d1389284570b163f6aa12622d15c6b6ecea17 Mon Sep 17 00:00:00 2001 From: Chuck Lever Date: Mon, 24 Sep 2007 11:28:33 -0400 Subject: [PATCH] mount.nfs: add EX_SUCCESS exit code We've had some recent trouble, especially in the umount code, that appears to be due to functions returning a 1 or a 0 return code when they should be returning a mount exit code (such as EX_FAIL) or a 0. To help clearly distinguish these two classes of functions, define an EX_SUCCESS exit code, which is equal to zero. Signed-off-by: Chuck Lever Signed-off-by: Neil Brown --- support/include/xcommon.h | 1 + 1 file changed, 1 insertion(+) diff --git a/support/include/xcommon.h b/support/include/xcommon.h index 9e23d12..d1a4b18 100644 --- a/support/include/xcommon.h +++ b/support/include/xcommon.h @@ -36,6 +36,7 @@ extern void die(int err, const char *fmt, ...); extern void (*at_die)(void); /* exit status - bits below are ORed */ +#define EX_SUCCESS 0 /* no failure occurred */ #define EX_USAGE 1 /* incorrect invocation or permission */ #define EX_SYSERR 2 /* out of memory, cannot fork, ... */ #define EX_SOFTWARE 4 /* internal mount bug or wrong version */ -- 2.39.5