umount.cifs: don't build it by default
authorJeff Layton <jlayton@samba.org>
Tue, 30 Jun 2009 19:03:13 +0000 (15:03 -0400)
committerJeff Layton <jlayton@redhat.com>
Tue, 30 Jun 2009 19:03:13 +0000 (15:03 -0400)
commitf7250144ed06b00fc1fbf1854d38483c427fad87
tree036697dc0c1351ca97176e3fe33144f7486fd8bb
parent91a8cb851e1919a337310e2c699d8fcf76a55060
umount.cifs: don't build it by default

Now that the sanity checks for mount.cifs default to matching the
behavior of /bin/mount, then there is virtually no need for umount.cifs.
The only exception is when someone enables the loose setuid behavior in
mount.cifs.

If an unprivileged user mounts a share that isn't in /etc/fstab, then
/bin/mount won't allow that user to unmount it. In that situation,
umount.cifs will be necessary to allow unmounting the share.

Signed-off-by: Jeff Layton <jlayton@samba.org>
Acked-by: Steve French <smfrench@us.ibm.com>
source3/Makefile.in
source3/configure.in