| Re: [chrony-dev] rtcsync in chrony 3.5 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] rtcsync in chrony 3.5
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 10 Dec 2019 10:41:50 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1575970917; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GyY//aCy3fm6d+ksj1Qh5DxYVOVCxviK/FAHL8JkE9Q=; b=UvauXUv7ptylxQUqg2SCFjA6as4xZc1R/7fy2b7prV0xvh13iktG17VYodS0XJd/sPg/2M VyLw9To0kkSvDRnNL0nCdFZ2/symlyMa6JnxeMibSXhKF+/dN12+MzQGfYDOFs/fdiaCAp DE5La8BLi34379LC+SfXIqfKptKCsow=
On Mon, Dec 09, 2019 at 04:11:30PM +0700, Gerriet M. Denkmann wrote:
> I have some suspicion that rtcsync does no longer work in 3.5.
>
> set_sync_status has these lines:
> /* update the RTC by applying a step of 0.0 secs */
> apply_step_offset(0.0);
> last_rtc_sync = now;
> DEBUG_LOG("rtc synchronised”;
>
> So: maybe I should turn on some debug flags (how? - I am rather clueless) and look at some log-file (where?)
In order to see the debug message, the configure script needs to be
called with --enable-debug and the compiled chronyd binary with two -d
options.
I suspect the problem is that on more recent macOS versions chronyd
doesn't use the macOS-specific set_sync_status() function, but reuses
the NetBSD driver, which doesn't do the get and set operation.
If anyone could confirm that the NetBSD/FreeBSD kernel sets the RTC on
settimeofday()/clock_settime(), it could be enabled in the NetBSD
driver.
--
Miroslav Lichvar
--
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.