I am aware of the --preserve-env or -E flag in
sudo
, however, it seems like this flag causes sudo to act weird in Fedora.
I installed ranger
with LinuxBrew
, Here's what I get when I type in which ranger
as a non-root user:
$ which ranger
/home/linuxbrew/.linuxbrew/bin/ranger
And if I sudo,
$ sudo -E which ranger
which: no ranger in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)
$ sudo -E echo $PATH
/usr/lib64/qt-3.3/bin:/usr/share/Modules/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/david/bin:/home/david/.gem/ruby/2.6.0:/home/david/prog/flutter/bin:/home/david/go/bin:/home/linuxbrew/.linuxbrew/bin:/home/david/.local/bin:/snap/bin:/var/lib/snapd/snap/bin:/home/david/.gem/ruby/2.6.0:/home/david/go/bin:/home/linuxbrew/.linuxbrew/bin:/home/david/.local/bin:/snap/bin:/home/david/prog/flutter/bin
$ sudo -E ranger
sudo: ranger: command not found
But things get weirder:
sudo --preserve-env=PATH which ranger
/home/linuxbrew/.linuxbrew/bin/ranger
$ sudo --preserve-env=PATH ranger
sudo: ranger: command not found
Can anyone explain what the actual heck is going on here?
Any help will be appreciated!
Asked by David
(143 rep)
Mar 2, 2020, 12:54 AM
Last activity: Apr 9, 2020, 07:20 AM
Last activity: Apr 9, 2020, 07:20 AM