From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: slow ssh login on a cygwin machine
Date: Tue, 28 Feb 2012 15:03:00 -0000 [thread overview]
Message-ID: <20120228144939.GE23440@calimero.vinschen.de> (raw)
In-Reply-To: <4F4CE2D2.1070602@nokia.com>
On Feb 28 16:21, Ilya Dogolazky wrote:
> Hi !
>
> I'm running sshd on a windows machine. Since last weekend (I have
> not installed anything) the logging in via ssh started to take 5 to
> 20 seconds (it was less than 1 second before that). It doesn't
> matter from which machine I'm logging in (tried localhost, some
> another cygwin machine, 3 different Linux machines: both staying in
> the same room or 1000 km away).
This kind of delay is often a result of the process trying to
access some remote filesystem. Or, maybe you have DNS problems
on the server.
> And another pretty strange thing: the /var/log directory contains a
> file "lastlog" of size 445 Megabytes (445916640).
That size is not overly surprising. The size of the lastlog file
depends on the highest uid used to login into the system. In your case
you seem have pretty large uids. Every uid slot in lastlog takes
276 bytes. So you had login attempts from a user with a uid 1615639.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-02-28 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 15:00 Ilya Dogolazky
2012-02-28 15:03 ` Corinna Vinschen [this message]
2012-02-28 15:34 ` Ilya Dogolazky
2012-02-28 15:50 ` Corinna Vinschen
2012-02-28 16:55 ` Corinna Vinschen
2012-02-29 14:40 ` Ilya Dogolazky
2012-02-29 15:17 ` Corinna Vinschen
2012-08-29 20:12 ` bbcolo22
2012-08-29 20:42 ` Larry Hall (Cygwin)
2012-08-29 21:04 ` bbcolo22
2012-08-29 22:19 ` Christopher Faylor
2012-08-29 23:42 ` bbcolo22
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120228144939.GE23440@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).