| [chrony-dev] clock_gettime() support |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-dev] clock_gettime() support
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 27 Jan 2026 16:02:34 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1769526157; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=QLccoFi35/7xzvvgOeSjA5xF5kVic8R+2ihQsjxavNY=; b=RWakAt5DMbid2UBs4Uudn6Fa+uQ/Z7JDuysCQDeNRYMn1Qhtg3XTbvpmKxU++HB50NmbyC hHfv5bN6aynGqZnLf1GTENKOeAd7qhiKkX2p6lMVuKYwOIe+ul0QJTad0BU0ZgRYOlUHTn Bf/nlqW0NbkANOazkghfhQGT9b6nZn4=
Is it ok to assume all systems supported by chrony now provide the
standard clock_gettime(), working at least with CLOCK_REALTIME and
CLOCK_MONOTONIC?
There is a comment in the macOS driver that it's available only on
macOS 10.12 and later. Wikipedia says 10.11.6 was released on July 9,
2018.
I'm considering some changes in order to support synchronization of
Linux PHC and CLOCK_AUX clocks and it would simplify things if I could
just drop the gettimeofday() support and use the CLOCK_* identifiers
everywhere.
--
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.