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

[Chris Adams]

Once upon a time, David Newall <davidn@xxxxxxxxxxxxxxx> said:
> > - the standards say that time() returns seconds since the epoch in UTC
> >   _except_ explicity NOT including leap seconds
> 
> Don't believe everything you read.  For example, the time(2) man page
> says what POSIX does, but doesn't actually say that Linux also does the
> same.  It also says what you paraphrased above, but demonstrably that's
> not the case.  Man pages often are wrong in some details.  Hence RTSL.

I wasn't talking about man pages.  I already quoted the section from the
Single Unix Specification version 3 (which supersedes POSIX) that
explicitly says leap seconds are ignored (despite sometimes heated
disagreement, as seen repeated here).  The standard "seconds since the
epoch" is seconds since 1970-01-01 00:00:00 UTC but not including leap
seconds (00:00:00 UTC is always 86400*n seconds since the epoch).

As long as Linux wants to work like all the other POSIX systems (which
it should unless there is huge advantage in doing otherwise), time(),
gettimeofday(), etc., all must work without leap seconds.

-- 
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
--
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/