From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: SSH Login Delay
Date: Mon, 21 Jan 2013 17:11:51 +0000 [thread overview]
Message-ID: <50FD76D7.1090209@communistcode.co.uk> (raw)
In-Reply-To: <50FD7553.50602@intel.com>
On 21/01/13 17:05, Scott Garman wrote:
> On 01/21/2013 07:21 AM, Jack Mitchell wrote:
>> I have recently noticed that when SSH'ing to my BeagleBone it has a 3-5
>> second delay before the bash prompt shows. I have looked in
>> /var/log/messages and noticed:
>>
>> Jan 18 15:47:12 beaglebone auth.info sshd[12389]: Accepted none for root
>> from 192.168.0.51 port 37905 ssh2
>> Jan 18 15:47:12 beaglebone auth.info sshd[12399]: lastlog_openseek:
>> Couldn't stat /var/log/lastlog: No such file or directory
>> Jan 18 15:47:12 beaglebone auth.info sshd[12399]: lastlog_openseek:
>> Couldn't stat /var/log/lastlog: No such file or directory
>>
>> I was wondering if these stat commands had a timeout on them and
>> therefore causing the delay. If so, why do these logs not exist?
>>
>> I have also noticed that avahi has crept into my image recently and if
>> it was possibly something to do with dns resolution or similar?
>
> In my experience this is most likely due to DNS resolution timing out
> trying to resolve a LAN IP address.
>
> Try editing the sshd_config on your BeagleBone's filesystem and set
> UseDNS to no. See if that helps.
>
> Scott
>
Perfect, fixed it straight away, thanks!
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
prev parent reply other threads:[~2013-01-21 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 15:21 SSH Login Delay Jack Mitchell
2013-01-21 17:05 ` Scott Garman
2013-01-21 17:11 ` Jack Mitchell [this message]
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=50FD76D7.1090209@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/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