Hmmm... I wonder if it could be related to the same kind of problem on
other platforms though it seem a bit extreme on the VAX. On the Alpha I've
had similar problems when the reverse lookup in the DNS didn't work. A
login could take 10's of minutes to complete, and when I fixed the DNS
problem the login quite fast.

...just a thought...It might be worthwile checking if it is related in
some way.

Cheers,
Anders

--
This mail was sent on Thu 04/28/05 at 5:53PM PDT


No problem is insoluble.
		-- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4

*************************************************************************
* Anders Hogrelius       Cell :  +46(0)70 884-2775, +46(0)70 677-0210
* Tessingatan 12         Phone:  +46(0)8 501-64524, +1(714)408-7868
* SE-72216 Vasteras      E-mail: anders@hogrelius.nu
* SWEDEN		 Web:    http://www.hogrelius.nu/~ahs/

On Thu, 28 Apr 2005, M J Dowden wrote:

>
> At 3:58 PM -0700 4/28/2005, Marat BN wrote:
> >Hi,
> >
> >Came across your communications regarding this problem
> >at
> >http://mail-index.netbsd.org/port-vax/2003/02/11/0004.html
> >
> >I'm having the same problem here.  I have an automated
> >task which keeps
> >sshing into the server again and again every 30
> >seconds to confirm that the
> >SSH daemon is up and running.  The sshd is hogging 99%
> >of CPU at the time
> >the automated task or someone else logs in via SSH.
> >
> >I see your post is back from 2003.  I'd like to check
> >if since then you were
> >able to find the any possible causes and/or
> >workarounds to reduce this
> >problem?
>
>
>      Sorry, but no. I just stopped using ssh2 and went back to ssh1.
> The problem was simply that ssh2 in one version worked fine, but in
> the next version of the OS, it became unusably slow.
>
>
>      Best regards,
>      M J Dowden
>
>
> --
> M J Dowden <mjdowden@panix.com>
> PGP key: <http://www.panix.com/~mjdowden/keys.shtml>
> No Microsoft products were used in the preparation or transmission of
> this message
>