| Re: [chrony-dev] When will chrony release next? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On 16/08/2018 04:40, Miroslav Lichvar wrote:
On Thu, Aug 16, 2018 at 12:11:00AM -0300, Gustavo Serra Scalet wrote:
I'm building Debian releases for cloud usage and noticed the known-issue[1]
regarding `getrandom` hanging when Chrony is called early on system boot
(and it does, as DHCP will call it during network configuration). I see it
as critical as ithappens every time on current snapshot builds after
booting. (`systemd-analyze` reports thgat startup times soared from 15
seconds to 180 seconds!)
Yeah, this is an annoying bug. I was hoping it would be addressed on
the kernel side as there are other applications affected by it and at
least some people seem to think the system call should never block
with the urandom source >
As I read on Ubuntu cloud[1], there are indeed other ways to handle this
and it would mitigate this issue on other projects as well, however it's
not the fastest solution so it should be planned accordingly.
On my specific workload, chrony is the only one being affected by this
behavior.
Are you planning to do a new release soon?
I was planning to make a new release in about a month, depending on
how much time I'll have for chrony. There is just one new feature left
on my todo list and then I'll be writing tests for the new code, etc.
One month looks good for me. Thanks! If it's blocking me too much, I'll
consider patch it downstream then.
If people think it's important enough, I could make a quick 3.3.1 bug
fix only release. I'm not sure.
Also a good solution for me, but it's your call.
Regards
[1]
https://blog.dustinkirkland.com/2014/02/random-seeds-in-ubuntu-1404-lts-cloud.html
--
Gustavo Serra Scalet
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.