[blfs-support] Unbound slow to start with recent kernels on some machines

Ken Moffat zarniwhoop at ntlworld.com
Mon Jun 25 10:46:12 PDT 2018


On Sun, Jun 24, 2018 at 09:36:52PM +0100, Ken Moffat wrote:

> 
> So I'm guessing that keying Ctrl-C one or more times, and possibly
> <enter>, generates enough entropy.
> 
> I have the random script at S25, but unbound is at S21.  The script
> intialises /dev/urandom, of course, but unbound is supposed to fall
> back to that (although the post on unbound-users suggests it didn't
> in that setup).
> 
> According to the documentation for the unbound bootscript, it
> relies on network (S20) so moving random to S21 would give me
> 
> S20network
> S21random
> S21smartd
> S21unbound
> 
> I'm not intending to reboot at the moment (on this machine I
> suspend, on the other main desktop I hibernate), will try to
> remember to change that on whichever machine I next intend to
> reboot.
> 

Tried that on my haswell, where I had needed to use Ctrl-C, Ctrl-C,
<enter> to (I originally thought) stop whatever was hanging.  No
change, but just keying Ctrl-C three times was good enough - and I
now guess that hitting any key(s) three tiem will do.

ĸen
-- 
              Keyboard not found, Press F1 to continue


More information about the blfs-support mailing list