public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: SSH Login Delay
Date: Mon, 21 Jan 2013 15:21:00 +0000	[thread overview]
Message-ID: <50FD5CDC.6080604@communistcode.co.uk> (raw)

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?

Has anyone else noticed issues or is a problem with my specific build?

I am running near HEAD oe-core master with a custom distro based on Poky.

Regards,
Jack.

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




             reply	other threads:[~2013-01-21 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 15:21 Jack Mitchell [this message]
2013-01-21 17:05 ` SSH Login Delay Scott Garman
2013-01-21 17:11   ` Jack Mitchell

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=50FD5CDC.6080604@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