Re: [chrony-users] Chrony vs. Linux RNG

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]


On 04/23/18 12:13, Miroslav Lichvar wrote:
On Mon, Apr 23, 2018 at 11:52:00AM +0200, Holger Hoffstätte wrote:
Gentoo using OpenRC, chronyd 3.3. It uses start-stop-daemon and it
was definitely chronyd hanging the boot sequence; for tests I disabled
chronyd from the default runlevel and all was back to smooth sailing.
Since s-s-d relies on chronyd going into the background, the temporary
fix was to add the --background flag to s-s-d so that OpenRC returns
immediately.

Ok, if it is blocking before the foreground process exits, that
probably means it's not due to NTP, but something else is using random
numbers, e.g. a timer is added to the scheduler.

I found in util.c that it *should* be using getrandom() already?

It should and that's probably why it is blocking. If you disable
HAVE_GETRANDOM, it should stop.


Indeed it does. I configured as usual but added a swift
"sed -i '/HAVE_GETRANDOM/d' config.h" post-configure, built,
removed the --background flag from s-s-d, rebooted and it
immediately starts just as before.

Now trying the other patch. :)

thanks!
Holger

--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject. For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/