LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   commands not working (https://www.linuxquestions.org/questions/fedora-35/commands-not-working-711295/)

pavan.manipal 03-13-2009 05:34 AM

commands not working
 
Why i am unable to run all commands that usually works on redhat , but not working in fedora 9?
ex: chkconfig whn i typed it shows command not there
but man chkconfig ,it works fine,
and then ifconfig, xinetd -service is not avilable, like wise do i have to do any changes in fedora to enable all commands?

b0uncer 03-13-2009 05:37 AM

Did you try running them as a regular user, or logged in as root (either through a login program, or "su -" or similar)? If you were logged in as a normal user or otherwise had non-root environment, the sbin/ directories may not have been in the $PATH variable, and thus any executables there will not be "found" when you type in their name without full path.

Try
Code:

su -
ifconfig

if it still doesn't work, there's something odd going on.

The other way, if you don't have the directories in $PATH, is to simply run them with full path to the executable.

pavan.manipal 03-13-2009 06:30 AM

i got the answer
 
hi guys dont worry about these "command not found" caution, just set the environment variable u can access all the commands , i did my self
export PATH=$PATH:/sbin/
type it njoy the fedora;
actually the variables are set by default
here we have to set

repo 03-13-2009 06:54 AM

Quote:

export PATH=$PATH:/sbin/
/sbin is by default not in the path from user with a reason.
It is only in the path from root.
You need root privileges to use them,

pavan.manipal 03-14-2009 05:11 AM

Quote:

Originally Posted by repo (Post 3474193)
/sbin is by default not in the path from user with a reason.
It is only in the path from root.
You need root privileges to use them,

i am using my comp with root privilages

repo 03-14-2009 05:39 AM

Quote:

i am using my comp with root privilages
Why would you do that?
Are you aware of the security risks?
Please don't do that, it's stupid.

pavan.manipal 03-14-2009 06:15 AM

Quote:

Originally Posted by repo (Post 3475155)
Why would you do that?
Are you aware of the security risks?
Please don't do that, it's stupid.

actually m using VMware for linux

pixellany 03-14-2009 06:51 AM

How is VMWare relevant?

What repo is trying to say is that running anything as the "root" or administrative user is not a good idea.

Note that running with root privileges is not the same as "running as root". For example, if you get root privileges using "su", you do not get the root environment. For that, do "su -".

pavan.manipal 03-14-2009 07:02 AM

Quote:

Originally Posted by pixellany (Post 3475207)
How is VMWare relevant?

What repo is trying to say is that running anything as the "root" or administrative user is not a good idea.

Note that running with root privileges is not the same as "running as root". For example, if you get root privileges using "su", you do not get the root environment. For that, do "su -".

thnx bro


All times are GMT -5. The time now is 08:14 AM.