Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
I have recently installed Redhat. Everything is working fine except when I telnet into the box using the telnet-server most of the commands are not available. They are however available in a local terminal. Even in the telnet session when I su to root they are still not there. Any ideas why this could be? Is there a file somewhere that disables sersitive functions for example?
Like say for instance I try and run 'chkconfig', I get the following:-
bash: chkconfig: command not found
It's the same for most commands involving services and daemons. In the process of setting up Poptop and things like 'modprobe' and 'lsmod' give the same response of command not found. Things like 'rpm', 'telnet', 'ftp' etc work fine... I'm quickly becoming confused lol.
Run:
echo $PATH
to see which directories it is searching for binaries.
On some systems the /sbin and /usr/sbin (Think system binaries: /sbin/lsmod) aren't in your path. When you su to root, you may need to run "su -", as this initializes root's environment (PATH HOME and such).
To fix this, you need to look at your .profile (or .bash_profile) and .bashrc. The first get run at login (telnet) time and may not source .bashrc. One fix is to put "PATH=/sbin:/usr/sbin:$PATH" into .profile (assuming you are running bash or other bourne compatible shells).
I don't have a mandrake box here right now, so I don't know what they do. Post back if you need more pointers.
Thats sorted it thanks... Put the 'PATH=/sbin:/usr/sbin:$PATH' into the file you said and that did it. The existing PATH was everything except the 'sbin' directories.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.