diff options
| author | Steinar H. Gunderson <sesse@debian.org> | 2007-07-14 11:18:48 +0200 |
|---|---|---|
| committer | Neil Brown <neilb@suse.de> | 2007-07-16 10:58:57 +1000 |
| commit | 4cd30380ba2e841511f1cb834a7163671ea1187e (patch) | |
| tree | ae5ab88ed64e576500da4d16017a64c8c79a78bd | |
| parent | 46ef88e0f7ec187e4448230efa6baf698643d3f9 (diff) | |
| download | nfs-utils-4cd30380ba2e841511f1cb834a7163671ea1187e.tar.gz nfs-utils-4cd30380ba2e841511f1cb834a7163671ea1187e.tar.xz nfs-utils-4cd30380ba2e841511f1cb834a7163671ea1187e.zip | |
Fix umount.nfs exit status
Hi,
As per a bug report from a user:
mount.c seems to assume that nfsumount() uses standard C true/false
return values, and inverts them for the exit status (where 0 is
traditionally considered success). However, nfsumount() consistently
seems to use 0 for success, and thus a success gets returned as exit
status 1 and a failure as exit status 0. This confuses at least
the GNOME drive manager applet, and probably others as well.
Signed-off-by: Steinar H. Gunderson <sesse@debian.org>
Signed-off-by: Neil Brown <neilb@suse.de>
| -rw-r--r-- | utils/mount/mount.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/utils/mount/mount.c b/utils/mount/mount.c index 442ce0e..17c79e4 100644 --- a/utils/mount/mount.c +++ b/utils/mount/mount.c @@ -399,7 +399,7 @@ int main(int argc, char *argv[]) umount_usage(); exit(1); } - exit(nfsumount(argc, argv) ? 0 : 1); + exit(nfsumount(argc, argv)); } if(argv[1] && argv[1][0] == '-') { |