Ok, this is a rather weird and embarrasing question, 'cause I should know what the answer is...
Anywho, when I ssh into a machine that shall remain un-named, I get this odd network problem. It's like this, I send data, say a command like 'ls -l' to the remote machine. If the response is large, say there are a large number of files in the dir in which I 'ls -l''d, basically some of the data will be written to the screen, and everything will freeze (kinda). That is, no more data will be displayed until I hit a key or otherwise send some data to the remote machine. To be clear, it goes like this: ssh into remote machine, cd to directory containing a large amount of files type 'ls -l' now, only the first part of the directory listing will be displayed (presumably, what fits into the first packet) In order to see the entire results, I have to hit a key, and the rest will be displayed (if the rest of the results fits into the next packet, otherwise I have to keep sending in order to recieve). This is just an example, this happens with things other than ls. I'm guessing that this is some TTY thing. That is, there is some "flow control" setting or something that is futzed. But, I nothing looks like an obvious solution. I vaguely remember stuff like this happening in the BBS days... namaste, Mark _______________________________________________ Siglinux mailing list [EMAIL PROTECTED] http://machito.utacm.org/mailman/listinfo/siglinux
