On 07/03/14 14:06, Miroslav Lichvar wrote:
> This is probably related to the new detection of forward time jumps,
> which was mainly intended to handle system suspends. When chronyd
I read that in the release notes and figured as much. :-)
> When this happens, in the log you should see a
On 01/28/15 12:47, Miroslav Lichvar wrote:
> On Wed, Jan 28, 2015 at 10:38:14AM +0100, Holger Hoffstätte wrote:
>> On 01/27/15 15:12, Miroslav Lichvar wrote:
>>> The first prerelease for chrony-2.0 is now available.
>>
>> Just some quick feedback since I haven't
Hi,
Peter Humphrey recently posted about his findings with an apprently
racy init script, see: https://bugs.gentoo.org/show_bug.cgi?id=566972
So far we've concluded that indeed the init script is inherently racy
due to accidental double-forking. I've since then investigated this a
bit more (see
...and of course I get to answer my own question. :)
> I haven't looked at the source yet, but it seems to me that loading and
> verifiying the configuration should not take several seconds before
> forking and returning. I don't have a ton of sources (2), they are all
> inhouse, healthy,
On 09/21/17 13:54, Chris Perl wrote:
> I would like a way to be able to ask chronyd not to combine time from
> multiple sources, but instead to just trim the local clock from the
> selected system peer.
Are you looking for the "combinelimit " directive?
If I understand you correctly,
Hello!
I test stable/LTS kernels to help Greg KH and just updated to 4.16.4-rc1.
This contains a few patches that are supposed to help with CVEs around
randomness, and which cause an interesting catch-22 that affects chrony,
hence this mail.
The patches in question are in the stable queue and
On 04/23/18 11:04, Miroslav Lichvar wrote:
On Sun, Apr 22, 2018 at 07:15:12PM +0200, Holger Hoffstätte wrote:
I test stable/LTS kernels to help Greg KH and just updated to 4.16.4-rc1.
This contains a few patches that are supposed to help with CVEs around
randomness, and which cause
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
On 04/23/18 12:40, Miroslav Lichvar wrote:
On Mon, Apr 23, 2018 at 12:05:55PM +0200, Holger Hoffstätte wrote:
So it's probably indeed blocking in too-early getrandom() (thanks for
pointing that out!)and falling back to urandom with GRND_NONBLOCK could
work. Let me know if I can try any patches
On 04/23/18 11:52, Holger Hoffstätte wrote:
I guess it could use a non-blocking read for the urandom device (or
getrandom() syscall) and fall back to random(), but I'm not sure if it
would be a good idea from the security point of view.
I found in util.c that it *should* be using getrandom
On 4/10/20 12:08 AM, Watson Ladd wrote:
On Wed, Apr 8, 2020 at 3:23 PM Watson Ladd wrote:
On Wed, Apr 8, 2020 at 5:58 AM Luca BRUNO wrote:
Hi all,
I'm following up from this old thread from 2016 regarding monitoring
chrony [0], and from this more recent discussion in Prometheus land [1].
On 4/8/20 11:00 AM, Lars-Daniel Weber wrote:
Hey Holger,
Holger wrote:
an important point for you since you're presumably in Germany and
Jawoll, under protection of CoronaSchVO NW.
I already went through the futile attempts to use these servers:
they're all outside Germany, with rather
On 3/31/20 1:18 AM, Jason W. Lewis wrote:
I’m looking at using chrony on our network for the first time, and
want it to accept the ntp-servers DHCP option. Does it? And if so,
how? I haven’t seen any documentation showing how to do this, so I
suspect it’s not supported, but at the same time,
On 2021-05-17 09:15, Miroslav Lichvar wrote:
On Sat, May 15, 2021 at 09:11:03PM -0700, w...@comcast.net wrote:
After a ".configure" and "make" after fetching
https://download.tuxfamily.org/chrony/chrony-4.1.tar.gz, "chronyd -v"
reports:
chronyd (chrony) version DEVELOPMENT (+CMDMON +NTP
On 2021-04-04 22:44, Uwe Fechner wrote:
Dear all,
I am trying to configure chrony with nts support, but so far it doesn't work:
ufechner@TUD277255:~/00Software/chrony-4.0$ ./configure
Configuring for Linux-x86_64
Checking for nettle : Yes
Checking for CMAC in nettle : No
Checking for
Hello chrony-users -
Some of you may remember past threads about monitoring chrony (e.g. [1]),
preferrably with Prometheus but without adding a hard dependency on
output formats or an http server within chrony itself.
Well..rejoice!
Ben Kochie has started an external exporter project which
On 2024-04-19 16:40, Chris Knox wrote:
Bryah, thanks for the answer. Yes, now that we have the scars, we're
monitoring chronyd's health carefully. But my question goes a bit
Glad you're back up and running.
Just to make sure since the details/constraints of your operational
setup were not
17 matches
Mail list logo
