[SOLVED] Eterm path or ?? not allowing usr/bin commands?

BW-userx · 10-29-2022, 05:46 PM

Quote:

userx@slackdog:~$ sudo
usage: sudo -h | -K | -k | -V
usage: sudo -v [-ABkNnS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-ABkNnS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
[command]
usage: sudo [-ABbEHkNnPS] [-C num] [-D directory] [-g group] [-h host] [-p
prompt] [-R directory] [-T timeout] [-u user] [VAR=value] [-i|-s]
[<command>]
usage: sudo -e [-ABkNnS] [-C num] [-D directory] [-g group] [-h host] [-p
prompt] [-R directory] [-T timeout] [-u user] file ...
userx@slackdog:~$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/libexec/kf5:/usr/lib64/qt5/bin
userx@slackdog:~$ whereis sbofind
sbofind: /usr/sbin/sbofind /usr/man/man1/sbofind.1.gz

it sees all of that until I put it together

Quote:

userx@slackdog:~$ sudo sbofind
sudo: sbofind: command not found

does anyone remember what goofball reason that Eterm does not see it, and how to fix it?

it is in root or something (for slackers) because it has them quotes when I open the terminal.

michaelk · 10-29-2022, 09:48 PM

whereis uses a hard coded path and not the users environment.

"sudo sbofind" I believe would still use the users path environment which does not include /usr/sbin/ and hence the command not found error.

"sudo -i sbofind" should use root's environment which should include /usr/sbin.

BW-userx · 10-31-2022, 03:34 PM

Code:

begin toggles
    map_alert 1
    urg_alert 0
    visual_bell 0
    login_shell 0
    scrollbar 1
    utmp_logging 1

changed login_shell 0 in saved user.conf