On Fri, Jan 02, 2004 at 09:41:45AM -0600, Mark wrote: > 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...
you can always try on the remote and local ends, messing with flow control via stty (i think (-)ixon is what's relevant), but i somehow don't think that's the problem. i don't really understand flow control myself, though. what it sounds more like to me is a poor implementation of the nagle algorithm which groups i/o bytes for transmission in bigger chunks over the network since there's such tremendous overhead for sending, say, a single character typed in a telnet connection as a tcp packet (not just the packet headers, but factor in the response that's generated as well). check your ssh client/server for nagle-related options, but it's more likely to be implemented in the network stack--ie pppd does it for you. still the behavior you report is not what nagle does when it works right (wait forever for input to continue output) so something's futzed somewhere. sorry to not be as helpful as i'd hoped... luck++; _______________________________________________ Siglinux mailing list [EMAIL PROTECTED] http://machito.utacm.org/mailman/listinfo/siglinux
