[BACK]Return to TROUBLESHOOTING CVS log [TXT] [DIR] Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / sudo / doc

Diff for /embedaddon/sudo/doc/TROUBLESHOOTING between versions 1.1.1.3 and 1.1.1.4

version 1.1.1.3, 2013/07/22 10:46:11 version 1.1.1.4, 2013/10/14 07:56:34
Line 22  A) Sudo must be setuid root to do its work.  Either /u Line 22  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     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     been done for you by "make install" but you can fix it manually by
    running the following as root:     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:  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      effective uid is not 0, is /usr/local/bin/sudo on a file system with the
Line 31  A) The owner and permissions on the sudo binary appear Line 31  A) The owner and permissions on the sudo binary appear
    sudo ran, the setuid bit did not have an effect.  There are two common     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     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     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   setuid binaries.  The output of the "mount" command should tell you if
   file system that is exported without root privileges.  By default, NFS   the file system is mounted with the 'nosuid' option.  The other possible
   file systems are exported with uid 0 mapped to a non-privileged uid   cause is that sudo is installed on an NFS-mounted file system that is
   (usually -2).   exported without root privileges.  By default, NFS file systems are
   exported with uid 0 mapped to a non-privileged uid (usually -2).  You
You need to do something like   should be able to determine whether sudo is located on an NFS-mounted
   `chmod 4111 /usr/local/bin/sudo'.  Also, the file system sudo resides   filesystem by running "df `which sudo'".
   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. 
   
 Q) Sudo never gives me a chance to enter a password using PAM, it just  Q) Sudo never gives me a chance to enter a password using PAM, it just
    says 'Sorry, try again.' three times and exits.     says 'Sorry, try again.' three times and exits.
Removed from v.1.1.1.3  
changed lines
  Added in v.1.1.1.4

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>