Groups | Search | Server Info | Login | Register

Groups > comp.software.year-2000 > #151

Re: Splunk has Y2.02k bug AND UNIX time_t bug ; 32768h SSD bug

Show all headers | View raw

In article <2ebe9e1f-7da5-4302-966b-89f223a8a16b@googlegroups.com>,
 <dr.j.r.stockton@gmail.com> wrote:
>On Wednesday, 18 December 2019 22:23:12 UTC, dr.j.r...@gmail.com  wrote:
>> See Risks Digest 31.50 in
>https://groups.google.com/forum/#!forum/comp.risks or elsewhere,
>articles :
>> 
>>  * This might be a genuine Y2K problem -- are there more? (Martyn Thomas)
>>  * ...
>> 
>> and what they each link to.
>> 
>> Both seem to refer to Y2K-class potential computer chaos/disaster
>> generators.
>
>
>See also, in http://catless.ncl.ac.uk/Risks/31/54, "A lazy fix 20 years
>ago means the Y2K bug is taking down computers now (New Scientist)" by
>Paul Saffo.

From the abovegiven URL:

--begin quoted text:

Coders chose 1920 to 2020 as the standard window because of the 
significance of the midpoint, 1970. "Many programming languages and 
systems handle dates and times as seconds from 1970/01/01, also called 
Unix time," says Tatsuhiko Miyagawa, an engineer at cloud platform 
provider Fastly.

--end quoted text

Most systems I worked on used a CENTWIN of 45.

DD

Back to comp.software.year-2000 | Previous | Next — Previous in thread | Find similar

Thread

Splunk has Y2.02k bug AND UNIX time_t bug ; 32768h SSD bug dr.j.r.stockton@gmail.com - 2019-12-18 14:23 -0800
  Re: Splunk has Y2.02k bug AND UNIX time_t bug ; 32768h SSD bug docdwarf@panix.com () - 2019-12-19 01:04 +0000
  Re: Splunk has Y2.02k bug AND UNIX time_t bug ; 32768h SSD bug dr.j.r.stockton@gmail.com - 2020-02-01 15:30 -0800
    Re: Splunk has Y2.02k bug AND UNIX time_t bug ; 32768h SSD bug docdwarf@panix.com () - 2020-02-02 03:59 +0000

csiph-web