summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2007-09-24 11:28:33 -0400
committerNeil Brown <neilb@suse.de>2007-09-25 11:50:15 +1000
commitd54d1389284570b163f6aa12622d15c6b6ecea17 (patch)
treeee3787c4dfedd35469cc9ca512241690ce1a5a0c
parentbda03ca689ff8b410a778299e5c6f4a14fcc85f8 (diff)
downloadnfs-utils-d54d1389284570b163f6aa12622d15c6b6ecea17.tar.gz
nfs-utils-d54d1389284570b163f6aa12622d15c6b6ecea17.tar.xz
nfs-utils-d54d1389284570b163f6aa12622d15c6b6ecea17.zip
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 <chuck.lever@oracle.com> Signed-off-by: Neil Brown <neilb@suse.de>
-rw-r--r--support/include/xcommon.h1
1 files changed, 1 insertions, 0 deletions
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 */