Date: Sat, 4 Oct 1997 10:02:51 +0930 From: Greg Lehey <grog@lemis.com> To: Steve Hovey <shovey@buffnet.net> Cc: Dave Hummel <hummel@www.buffalostate.edu>, questions@FreeBSD.ORG Subject: Re: slow telnet Message-ID: <19971004100251.36524@lemis.com> In-Reply-To: <Pine.BSI.3.95.971003085933.28200G-100000@buffnet11.buffnet.net>; from Steve Hovey on Fri, Oct 03, 1997 at 08:59:55AM -0400 References: <19971003152114.25106@lemis.com> <Pine.BSI.3.95.971003085933.28200G-100000@buffnet11.buffnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 03, 1997 at 08:59:55AM -0400, Steve Hovey wrote:
> On Fri, 3 Oct 1997, Greg Lehey wrote:
>
>> On Thu, Oct 02, 1997 at 02:15:14PM -0400, Steve Hovey wrote:
>>>
>>> I notices here starting with 2.1R that an rlogin would be slow in direct
>>> inverse proportion to the stty baud rate setting.
>>>
>>> So at a $ prompt type stty 9600 and see if it suddenly speeds up.
>>
>> No, this is incorrect. It has no effect on an IP connection.
>
> It does for rlogin - and is most noticible on slower modems.
How do you measure this?
This can't work. IP just doesn't work that way. Of course, it's just
barely possible that you have uncovered some bug, but I just couldn't
imagine where. Anyway, just to check, I've set up an rlogin to
FreeBSD.org. I then timed running a 'ps aux'. Here are the results:
=== grog@hub (/dev/ttypk) ~ 2 -> stty -a
speed 9600 baud; 70 rows; 120 columns;
lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
-extproc
iflags: -istrip icrnl -inlcr -igncr -ixon -ixoff ixany imaxbel -ignbrk
brkint -inpck -ignpar -parmrk
oflags: opost onlcr -oxtabs
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow
-dtrflow -mdmbuf
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
eol2 = <undef>; erase = ^H; intr = ^C; kill = ^U; lnext = ^V;
min = 1; quit = ^\; reprint = ^R; start = ^Q; status = <undef>;
stop = ^S; susp = ^Z; time = 0; werase = ^W;
=== grog@hub (/dev/ttypk) ~ 3 -> time ps aux
...
root 3 0.0 0.0 0 12 ?? DL 7Jun97 20:01.45 (vmdaemon)
1.92 real 0.10 user 0.29 sys
=== grog@hub (/dev/ttypk) ~ 6 -> stty speed 50
9600
=== grog@hub (/dev/ttypk) ~ 7 -> stty -a
speed 50 baud; 70 rows; 120 columns;
lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
-extproc
iflags: -istrip icrnl -inlcr -igncr -ixon -ixoff ixany imaxbel -ignbrk
brkint -inpck -ignpar -parmrk
oflags: opost onlcr -oxtabs
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow
-dtrflow -mdmbuf
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
eol2 = <undef>; erase = ^H; intr = ^C; kill = ^U; lnext = ^V;
min = 1; quit = ^\; reprint = ^R; start = ^Q; status = <undef>;
stop = ^S; susp = ^Z; time = 0; werase = ^W;
root 2 0.0 0.0 0 12 ?? DL 7Jun97 87:41.77 (pagedaemon)
=== grog@hub (/dev/ttypk) ~ 8 -> time ps aux
...
0.46 real 0.07 user 0.30 sys
=== grog@hub (/dev/ttypk) ~ 9 ->
The difference in time is coincidental; the net's a bit congested
today. The fact is, stty is talking to a pty, which doesn't transmit
data serially, so there is nowhere for the bit rate to be applied. In
any case, the pty runs only locally. You might just as well set the
bit rate on a console window or an xterm.
In general, people: if you have a suspicion that a problem may be due
to something you have discovered, and you're not deep gurus in the
area, check the details before you broadcast it to the world. It can
save embarrassment.
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971004100251.36524>