Re: Bug: Status/Summary of slashdot leap-second crash on new years2008-2009

[David Newall]

Kyle Moffett wrote:
> Actually, "diddling the clock" is really the only valid solution to
> the leap-second problem.  The leap-second is such a fine adjustment
> that it is actually affected by random "noise" introduced into the
> solar-system from the chaotic gravitational interactions of the
> planets with each other.  It's impossible to reliably calculate which
> future years will have leap seconds, and in which direction they will
> occur.
>   

You're confusing the system of keeping time with those characteristics
of the real-world which it represents.  They are, in fact, two different
things, hence we regularly adjust the system.  Now in the case of UNIX
and derivatives, the system records the number of seconds since an
arbitrary point-in-time, and presents a "wall time" (i.e. the time
displayed by the clock on the wall) using, amongst other things, a set
of adjustment rules codified by a zoneinfo file.  The number of second
between 1 minute to- and midnight-ending 31 December is 61.  If Linux
does not reflect that it is wrong and must be fixed.  If it isn't fixed
we will increasingly discover a discrepancy between time-data that
originates on Linux versus other, correct systems.

I don't understand why such a simple thing was unnecessarily
complicated.  And causing crashes!  Ha ha ha or what?  A simple addition
to zoneinfo was (and still is) all that is required.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/