X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=debian%2Fpatches%2F04-umount-exit-status.patch;fp=debian%2Fpatches%2F04-umount-exit-status.patch;h=bba5bfd8936bd5596ce1ff01f48da7c42a56b10c;hb=089e41fa4ca7123113984b1867ee5f22571e9bee;hp=0000000000000000000000000000000000000000;hpb=3a11169202f9db0eb8b07612396e78ddbc5600f1;p=nfs-utils.git

diff --git a/debian/patches/04-umount-exit-status.patch b/debian/patches/04-umount-exit-status.patch
new file mode 100644
index 0000000..bba5bfd
--- /dev/null
+++ b/debian/patches/04-umount-exit-status.patch
@@ -0,0 +1,20 @@
+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.
+
+Index: nfs-utils-1.1.0/utils/mount/mount.c
+===================================================================
+--- nfs-utils-1.1.0.orig/utils/mount/mount.c
++++ nfs-utils-1.1.0/utils/mount/mount.c
+@@ -371,7 +371,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] == '-') {