3 ms·
> Each Unix timestamp corresponds to one unique point in time which also has some representation in civil time This is plain false. For example 1435708799 corr
by zokier 3y ago
> Each Unix timestamp corresponds to one unique point in time which also has some representation in civil time
This is plain false. For example 1435708799 corresponds to both 2015-06-30T23:59:59Z and 2015-06-30T23:59:60Z
- morelisp 3y agoNo, your misdesigned ntpd resets your clock to 1435708799 at 2015-06-30T23:59:60Z. I have yet to see a convincing argument that smearing and freezing are not compatible with POSIX's definitions of time.
- zokier 3y agoits kernel that does the leap second handling, ntpd just informs it of upcoming leaps https://elixir.bootlin.com/linux/v6.4.1/source/kernel/time/ntp.c#L406 https://elixir.bootlin.com/linux/v6.4.1/source/kernel/time/n... sure leap smearing could be considered compatible with posix in the sense that posix does afaik not require any level of accuracy from clocks, so even something silly like xkcd 2266 could be considered posix compatible https://xkcd.com/2266/ https://xkcd.com/2266/