All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] SSH server starts too late
Date: Fri, 21 Feb 2020 11:19:47 +0100	[thread overview]
Message-ID: <20200221111947.33e4677d@gmx.net> (raw)
In-Reply-To: <CAGSpp9=qDFdtuETT8shQPXim25V7Yw2jvpjihbJgrttozOBVSQ@mail.gmail.com>

Hello Hammami,

On Fri, 21 Feb 2020 10:13:17 +0100, Hammami Omar <omar18hammami@gmail.com> wrote:

> Hello,
>
> I am using the buildroot version "2019.11.1" and I have noticed that my SSH
> server starts too late.
> I was using an old version "2017.08" and the SSH server was starting
> normally.
> Are you aware of this issue please ?
> And do you propose a workaround for this ?

What exactly do you mean by 'to late'? Which init system do you use?

On first boot the ssh keys must be generated (which can use some time
depending on the hardware and the random source)...., random generation
can be speed up by e.g. using/enabling haveged...

Regards,
Peter

> And thank you very much.
>
> Best regards,
> omar

  reply	other threads:[~2020-02-21 10:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  9:13 [Buildroot] SSH server starts too late Hammami Omar
2020-02-21 10:19 ` Peter Seiderer [this message]
2020-02-21 14:50   ` Hammami Omar
2020-02-21 16:16     ` Hammami Omar
2020-02-21 18:08     ` Grant Edwards
2020-02-21 18:30       ` Hammami Omar
2020-03-03 12:33         ` Hammami Omar
     [not found] <mailman.11.1582286403.41897.buildroot@busybox.net>
2020-02-21 12:51 ` Andreas Ziegler
2020-02-24  9:29   ` Hammami Omar
     [not found]     ` <1d91f38acaeecb790f5a44d104ae0ca1@umbiko.net>
2020-02-24 13:07       ` Andreas Ziegler
     [not found]       ` <CAGSpp9ng2yxCK=RZeq1Z_Bce4pwij9FQED23SpGuvjqm5awHhg@mail.gmail.com>
2020-02-24 13:22         ` Andreas Ziegler
2020-02-24 14:07           ` Hammami Omar
2020-02-24 15:16             ` Hammami Omar

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=20200221111947.33e4677d@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.