Re: [Sbcl-devel] get-internal-real-time and leap seconds

[Nicholas P. <npa...@gm...>]

I'll second that.  I've got a couple packages I've been working to
implement timer functions and rate-monotonic flow control (with none of the
normal rate-monotonic guarantees), using internal-real-time as the portable
time reference.  If internal-real-time jumps with system time, then my
packages just devolve to unreliable toys without a different timing backend.

On Tue, Jan 3, 2017 at 6:37 PM, Ilya Perminov <ipe...@dw...>
wrote:

> Hi all,
>
> I got bitten by the last leap second occurrence (on Dec 31). The Linux
> kernel stepped system time by a second, my code measured a negative
> time interval using get-internal-real-time, and died.
> get-internal-real-time uses "gettimeofday", which is affected by jumps in
> the system time.
> Do it make sense to utilize "clock_gettime (CLOCK_MONOTONIC, ...)" in
> get-internal-real-time (on OSes where CLOCK_MONOTONIC is available)?
>
> Thanks,
> Ilya
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Sbcl-devel mailing list
> Sbc...@li...
> https://lists.sourceforge.net/lists/listinfo/sbcl-devel
>
>