Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 Jul 2002 00:42:49 -0400 
From:      "Kellers, Timothy" <kellers@ADM.NJIT.EDU>
To:        "'Dan Nelson '" <dnelson@allantgroup.com>, "'Tim Kellers '" <timothyk@serv1.wallnet.com>
Cc:        "'questions@freebsd.org '" <questions@freebsd.org>, "'kellers@njit.edu '" <kellers@njit.edu>
Subject:   RE: NFS/NIS... arg!
Message-ID:  <E7DB63F7BA58D21195DD0000D110ADE00833BE20@adm.njit.edu>

next in thread | raw e-mail | index | archive | help
 I suppose that I could be less clear (if I worked at it), but...

The latency only exists during the login and authentication; then about 30
seconds elapses before the login is completed.  The slowness in echoing
characters back to the screen occurs during the login/authentication
process.  After the login is completed, speeds accessing files or services
are a bit sluggish, but nominally normal.

However when I boot the machine directly into X (/usr/local/bin/kdm
-nodaemaon), not only is the login process terribly slow, but the loading of
the desktop (from the remote home directory) and the execution of any of the
desktop programs is/are so slow as to be unusuable.

Tim Kellers
CPE/NJIT

-----Original Message-----
From: Dan Nelson
To: Tim Kellers
Cc: questions@freebsd.org; kellers@njit.edu
Sent: 7/9/02 12:37 AM
Subject: Re: NFS/NIS... arg!

In the last episode (Jul 09), Tim Kellers said:
> Not "snappy" means palpably slow.  Imagine a shared dialup network
> connection with more than one machine attempting downloads.
> 
> To be a bit more concrete, I can login via the CLI, but AI have to
> wait several seconds before my typed commands echo back on the
> originating workstation.  I think I've got some network gremlins to
> contend with but I appreciate any input you might have, and thanks
> for the reply.

So you're talking about latency typing characters at the shell prompt? 
That doesn't make much sense at all, assuming you're on a local
console.  If you're telnetting into the server, it sounds like bad
packet loss.  Try tcpdumping the telnet port on both client and server
and see what both ends are doing.

-- 
 Dan Nelson
 dnelson@allantgroup.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E7DB63F7BA58D21195DD0000D110ADE00833BE20>