Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I believe I have some sort of configuration problems with openssh on my RH9 box, even though I have all the defaults set. Everything that I am about to mentioned used to work, before I messed it up.
I can log in and navigate fine through the filesystem, but when I run commands like ls and ps that have a fairly long list of output, the first line will display to my shell and then it locks to all keyboard input further input/output. I am forced to disconnect and log in again.
I am using an SSH for client workstations. When I use this to log into an old school account, these commands are executed fine.
In addition, when I open the file transfer window, it says its "reading folder...please wait", but nothing happens and again the shell locks up and i have to restart.
Nope, just tried with putty and the same problem arrises. The test that I do is to list the files in a directory that has a large listing. For example, if I 'ls /usr/bin' nothing happens, and I no longer am able to type commands or even kill the [supposed to be] running process.
Using putty, with a ssh connection to my box, I opened an ftp session from that shell. I went to two picture folders that I have up, and when I listed the one with fewer pics (~17) it listed fine...the larger (~22), the 'ls' cmd did nothing, and the keyboard locked. This is the same when viewing ftp folders from other mediums such as a web browser.
It is like there is a setting limiting the number of files/directories or even lines (sending a ps -eaf command).
I have tried these same commands when logged onto other unix servers and I had no problems.
I have been trying to get mysql and php to work, just learning. As I am finding out, I am doing it the hard way. Instead of installing the rpm packages, I have been downloading the source and compiling it myself. I don't know if anything that I have been doing has affected it or not.
after that the keyboard locked up...crazy isn't it...some cmds go through, the one's that only send small lists to the screen, but you would think that larger outputs would be at least as long as the smaller ones that were able to complete?