| Re: [chrony-dev] [PATCH] macOS adjtime() faults with NULL request |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [PATCH] macOS adjtime() faults with NULL request
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 9 Aug 2017 10:32:51 +0200
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 9470B7DCC4
On Wed, Aug 09, 2017 at 05:14:05AM +1200, Bryan Christianson wrote:
> On some systems, passing NULL as the first argument to adjtime, will result in returning the amount of adjustment outstanding from a previous call to adjtime().
>
> On macOS this is not allowed and the adjtime call will fault. We can simulate the behaviour of the other systems by cancelling the current adjustment then restarting the adjustment using the outstanding time that was returned. On macOS 10.13 and later, the netbsd driver is now used and must use these semantics when making/measuring corrections.
Applied. Thanks.
--
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.