Feature changed by: Sławomir Lach (Lachu) Feature #310406, revision 4 Title: Make /sbin and /usr/sbin accessible by sudo out-of-the-box openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Jan Matejek (matejcik) Partner organization: openSUSE.org Description: In current situation, /sbin and /usr/sbin are excluded from user path. If the user wants to use 'sudo' to run superuser tools located in sbin, the command fails. Example: matejcik@ws-pool1:~> yast2 Absolute path to 'yast2' is '/sbin/yast2', so running it may require superuser privileges (eg. root). matejcik@ws-pool1:~> sudo yast2 sudo: yast2: command not found Sudo should be configured out-of-the-box to be able to find commands located in /sbin and /usr/sbin - either by modifying secure_path in /etc/sudoers, or putting sbin's back into default user paths. Business case (Partner benefit): openSUSE.org: One of the common scenarios for administering a Linux system is never logging in as root and using sudo to execute all superuser commands. This approach fails miserably in openSUSE, making it less comfortable for some power users, and much less accessible for users coming from other distributions (most notably Ubuntu, where the sudo approach is the officially sanctioned way of doing things) + Discussion: + #1: Sławomir Lach (lachu) (2010-08-27 12:23:32) + Why SUDO don't change search paths? + + I must mentoin, that current working direcotry isn't used to search + program. Why don't changing PATH on sudo? + + If somebody have good reason: I think, that sudo should add PATH to + ROOT_PATH:$PATH, where ROOT_PATH would been read from config file. This + force us to add new config rules and allow to change PATH depending on + destination UID. -- openSUSE Feature: https://features.opensuse.org/310406