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

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	2019-12-19 01:04 +0000
Organization	Public Access Networks Corp.
Message-ID	<qteibq$bju$2@reader2.panix.com> (permalink)
References	<b1d19726-203b-4637-843c-9321fa449076@googlegroups.com>

Show all headers | View raw

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

Back to comp.software.year-2000 | Previous | Next — Previous in thread | Next 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