In message: <6194.1164756521@xxxxxxxxxxxxxxxxxx>
"Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx> writes:
: given wall-clock (UTC) time.
UTC has leapseconds, and likely is adjusted by ntp.
: Others want to sleep on the absolute (TAI) timescale, such as TCP
TAI has no leapseconds and is a perfect monotonic timescale.
Warner
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
Re: hwclock problem with leapseconds - posix? ... always done in UTC,...clock your timestamps WILL be out, by far far more than any leapseconds.... as i understand djb's clockspeed can handle utc and tai sources,... (comp.os.linux.setup)
Re: hwclock problem with leapseconds - posix? ... could be viewed as merely different ways of labeling the stream of TAI... If I take the unix UTC date of now, ... the UTC seconds since epoch are out by 23 seconds. ... can either alter the calculation that date does to add on the leapseconds... (comp.os.linux.setup)
Re: hwclock problem with leapseconds - posix? ... preferably i also want the rtc updated during normal running system, ... You are using modified TAI,... I have no idea what a leapsecond respecting timezone is. ... served better by using UTC.... (comp.os.linux.setup)
Re: hwclock problem with leapseconds - posix? ... a quick look shows that hwclock uses the routines mktime with the timezone... I suspect that the assumption that we are using UTC, not TAI, and that the ... preferably i also want the rtc updated during normal running system, ... (comp.os.linux.setup)
Re: hwclock problem with leapseconds - posix? ...hwclock, then you have a bug in hwclock, a bug which djb should fix. ... hwclock does not handle leapseconds the same way on writing to rtc as ... system uses utc, then no use of zoneinfo should be done. ... (comp.os.linux.setup)
