MAJOR=4 MINOR=33 DEVNAME=tty33 ##l=J*h8pLl*bѿ ?#Troubleshooting tips and FAQ for Sudo ===================================== #### When I run configure, it says "C compiler cannot create executables". > This usually means you either don't have a working compiler. This > could be due to the lack of a license or that some component of the > compiler suite could not be found. Check config.log for clues as > to why this is happening. On many systems, compiler components live > in /usr/ccs/bin which may not be in your PATH environment variable. #### When I run configure, it says "sudo requires the 'ar' utility to build". > As part of the build process, sudo creates a temporary library > containing objects that are shared amongst the different sudo > executables. On Unix systems, the 'ar' utility is used to do this. > This error indicates that 'ar' is missing on your system. On Solaris > systems, you may need to install the SUNWbtool package. On other > systems 'ar' may be included in the GNU binutils package. #### Sudo compiles and installs successfully but when I try to run it I get: The "no new privileges" flag is set, which prevents sudo from running as root. If sudo is running in a container, you may need to adjust the container configuration to disable the flag. > Sudo was run by a process that has the Linux "no new privileges" > flag set. This causes the set-user-ID bit to be ignored when running > an executable, which will prevent sudo from functioning. The most > likely cause for this is running sudo within a container that sets > this flag. Check the documentation to see if it is possible to > configure the container such that the flag is not set. #### Sudo compiles and installs successfully but when I try to run it I get: /usr/local/bin/sudo must be owned by uid 0 and have the setuid bit set > Sudo must be set-user-ID root to do its work. Either `/usr/local/bin/sudo` > is not owned by user-ID 0 or the set-user-ID 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 4755 /usr/local/bin/sudo #### Sudo compiles and installs successfully 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 'nosuid' option set or an NFS file system without root privileges? > The owner and permissions on the sudo binary appear to be OK but when > sudo ran, the set-user-ID 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 set-user-ID 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 user-ID 0 mapped to a non-privileged ID (usually > -2). You should be able to determine whether sudo is located on an > NFS-mounted filesystem by running "df \`which sudo\`". #### Sudo never gives me a chance to enter a password using PAM It just says "Sorry, try again." three times and exits. > You didn't setup PAM to work with sudo. On RedHat or Fedora Linux > this generally means installing the sample pam.conf file as > /etc/pam.d/sudo. See the example pam.conf file for hints on what > to use for other Linux systems. #### Sudo says my account has expired but I know it has not > If you get the following error from sudo: Account expired or PAM config lacks an 'account' section for sudo, contact your system administrator` > double-check the `/etc/shadow` file to verify that the target user > (for example, root) does not have the password expiration field set. > A common way to disable access to an account is to set the expiration > date to 1, such as via `usermod -e 1`. If the account is marked as > ex