BASH: Command not found

evolotion · #1 25th January 2006, 10:59 PM

Having soem bother with my linux box (fc3) after a few uptates, alot of commands are not working, for example to run ifconfig i need to type in /sbin/ifconfig as just typing ifconfig yeilds a command not found error.

where is the config file that defines the paths? what is it called? as i assume its been deleted/changed/whatever.

landoncz · #2 25th January 2006, 11:17 PM

Just add the path "/sbin" to your path variable in your .bashrc file in your home directory (assuming you are using bash shell). C-shell is .cshrc...

evolotion · #3 25th January 2006, 11:33 PM

hmmm.. cheers, but my .bashrc looks like this : =
Cant see any path variable :S

Code:

# .bashrc

# User specific aliases and functions

alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'

# Source global definitions
if [ -f /etc/bashrc ]; then
	. /etc/bashrc
fi

landoncz · #4 26th January 2006, 12:23 AM

Try adding this to your bashrc file:

Code:

PATH=$PATH:/sbin
export PATH

This appends the path /sbin to your current path variable... should work...

Mat · #5 26th January 2006, 12:30 AM

add

Code:

PATH=$PATH:/sbin

to ~/.bash_profile

Mat

gavinw6662 · #6 26th January 2006, 05:49 AM

Quote:

Originally Posted by evolotion

Having soem bother with my linux box (fc3) after a few uptates, alot of commands are not working, for example to run ifconfig i need to type in /sbin/ifconfig as just typing ifconfig yeilds a command not found error.

where is the config file that defines the paths? what is it called? as i assume its been deleted/changed/whatever.

ifconfig is in /sbin which typically root has access too. Where you using root before, and not now?? Or where you sudo'd to root and never backed out??

evolotion · #7 26th January 2006, 01:53 PM

haveing this trouble with commands whether im SU'd into root or as a regular user. the ifconfig was an example, it happens with other commands aswell.

Mat · #8 26th January 2006, 03:00 PM

evolotion, changing to root with
$ su
is different than changing via
$ su -
!!

with the latter, you have root's path (including /sbin) and with the former, you are only left with the user's path that issued the "su" command (which does not include /sbin)..

have a look at
$ man su
for details

Mat

ibbo · #9 26th January 2006, 03:07 PM

Your best leaving it as is.

The advantages of this are if ever a program of yours is tampered with or another copy of a malicious version is installed then when you type ifconfig it will run the ifconfig from the first dir it finds in the search path. Which means if you have an ifconfig in your own bin dir then that will be run instead of /sbin/ifconfig. This was introcuced to linux years abck as an extra security measure. Looks like its going round full circle.

Dont sound like a big deal but it is when things go belly up. Besides after a while you start to know exactly where stuff is and adding and extra /sb -> TAB is not much typing thus not much bother.

Ibbo