Date: Tue, 22 Feb 2005 15:42:41 -0800 From: pete wright <nomadlogic@gmail.com> To: Jim Freeze <jim@freeze.org> Cc: questions@freebsd.org Subject: Re: SSH terminal locking up from OS X to FreeBSD Message-ID: <57d710000502221542173c5cef@mail.gmail.com> In-Reply-To: <20050222233640.GD34739@freeze.org> References: <20050222211148.GA39859@freeze.org> <421BAC56.4050801@daleco.biz> <20050222231352.GA34739@freeze.org> <57d710000502221532dbacb23@mail.gmail.com> <20050222233640.GD34739@freeze.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Feb 2005 23:36:40 +0000, Jim Freeze <jim@freeze.org> wrote: > > unless i'm missing something you are making the connection then typing > > exit in the shell. > > For this example, yes. That was the exit to leave the remote host. > I did this just to show that I had successfully logged in. If I > had waited a few minutes, then I would not have been able to show > that because the terminal would have locked up. > hmm...maybe it'll be more helpfull if you wait until it actually lock's on you and post that info. it also may be a good idea to run a tcpdump or ethereal (i think one of those utils is built into OSX's network utilites package) while this is happening. altho hopefully something interesting will pop up in the ssh debug output. also, are you able to check the logs on the the server end to see if anything makes it to there that may be of interest? HTH -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57d710000502221542173c5cef>