FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I am logged in as a user or as root, I am told that ifconfig isn't a valid command, so I figured that for some reason it wasnt put in my /usr/bin command list so i cd to the sbin dir where it is and tried it from there, still no luck. I have never had this problem before. What is up with this command?
while i am longed in as my self i still have the problem. if I su in i still have the problem. if i su - in idont have the problem, and if i directly log in as root i dont have the problem.
Are you just running "ifconfig" to see your interfaces, or are you assigning an IP or something? Meaning, is the issue possibly syntax? What do you get if you do a "which ifconfig" or a "type ifconfig"? In /sbin did you execute "ifconfig" or "./ifconfig"?
edit: I missed your last post - your problem is your "environment" and specifically your path. Either log in as root, or use "su -" to remedy the issue (as you've seen). This is not a bug, it's a feature.
ccerino--
reason is that the "su" command grants you root privs, but does NOT load the root user environment(more pointedly, you don't get root's "PATH" variable) doing the "su -" gets you root's path and IIRC home dir too. The same thing as logging in as root. It's not a problem, it's actually by design. By default only root can do ifconfig, and the system will only find it when root's enviro is loaded
ccerino--
reason is that the "su" command grants you root privs, but does NOT load the root user environment(more pointedly, you don't get root's "PATH" variable) doing the "su -" gets you root's path and IIRC home dir too. The same thing as logging in as root. It's not a problem, it's actually by design. By default only root can do ifconfig, and the system will only find it when root's enviro is loaded
dang...I just learned something today!!!!! Im such a newb
thxs
dareino
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.