--- embedaddon/sudo/doc/TROUBLESHOOTING	2013/07/22 10:46:11	1.1.1.3
+++ embedaddon/sudo/doc/TROUBLESHOOTING	2013/10/14 07:56:34	1.1.1.4
@@ -22,7 +22,7 @@ A) Sudo must be setuid root to do its work.  Either /u
    is not owned by uid 0 or the setuid bit is not set.  This should have
    been done for you by "make install" but you can fix it manually by
    running the following as root:
-    # chown root /usr/local/bin/sudo; chmod 4111 /usr/local/bin/sudo
+    # chown root /usr/local/bin/sudo; chmod 4755 /usr/local/bin/sudo
 
 Q) Sudo compiles and installs OK but when I try to run it I get:
     effective uid is not 0, is /usr/local/bin/sudo on a file system with the
@@ -31,17 +31,13 @@ A) The owner and permissions on the sudo binary appear
    sudo ran, the setuid bit did not have an effect.  There are two common
    causes for this.  The first is that the file system the sudo binary
    is located on is mounted with the 'nosuid' mount option, which disables
-   setuid binaries.  The other is that sudo is installed on an NFS-mounted
-   file system that is exported without root privileges.  By default, NFS
-   file systems are exported with uid 0 mapped to a non-privileged uid
-   (usually -2).
-
-You need to do something like
-   `chmod 4111 /usr/local/bin/sudo'.  Also, the file system sudo resides
-   on must *not* be mounted (or exported) with the nosuid option or sudo
-   will not be able to work.  Another possibility is you may have '.' in
-   your $PATH before the directory containing sudo.  If you are going
-   to have '.' in your path you should make sure it is at the end.
+   setuid binaries.  The output of the "mount" command should tell you if
+   the file system is mounted with the 'nosuid' option.  The other possible
+   cause is that sudo is installed on an NFS-mounted file system that is
+   exported without root privileges.  By default, NFS file systems are
+   exported with uid 0 mapped to a non-privileged uid (usually -2).  You
+   should be able to determine whether sudo is located on an NFS-mounted
+   filesystem by running "df `which sudo'".
 
 Q) Sudo never gives me a chance to enter a password using PAM, it just
    says 'Sorry, try again.' three times and exits.