Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!not-for-mail
From: docdwarf@panix.com ()
Newsgroups: comp.software.year-2000
Subject: Re: Splunk has Y2.02k bug AND UNIX time_t bug ; 32768h SSD bug
Date: Thu, 19 Dec 2019 01:04:58 +0000 (UTC)
Organization: Public Access Networks Corp.
Lines: 17
Message-ID: <qteibq$bju$2@reader2.panix.com>
References: <b1d19726-203b-4637-843c-9321fa449076@googlegroups.com>
NNTP-Posting-Host: panix1.panix.com
X-Trace: reader2.panix.com 1576717498 11902 166.84.1.1 (19 Dec 2019 01:04:58 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Thu, 19 Dec 2019 01:04:58 +0000 (UTC)
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: docdwarf@panix.com ()
Xref: csiph.com comp.software.year-2000:142

In article <b1d19726-203b-4637-843c-9321fa449076@googlegroups.com>,
 <dr.j.r.stockton@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)
> * SSD drive with critical failure at 32768 hours of operation (HPE)
>
>and what they each link to.
>
>Both seem to refer to Y2K-class potential computer chaos/disaster generators.

Some folks reading here survived a Y2K-class event almost two decades 
back.

DD