[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: ugh! (fwd)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: RE: ugh! (fwd)
  • Date: Mon, 3 Jan 2000 10:02:57 -0700 (MST)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Sat, 1 Jan 2000 00:14:34 -0500
From: Dan Vietor <address@hidden>
To: 'D. J. Raymond' <address@hidden>, address@hidden
Subject: RE: ugh!

Purdue is getting current data but the pqact Y2K bug is in effect there.
The files all start with "10".  Should I fix it for them??  Purdue uses
I believe Illinois for their primary.

________________________________________________________
Daniel Vietor               Mail: address@hidden
Unisys Corp                 Title: Engineer/Meteorologist
221 Gale Lane               Phone: 610-444-2407
Kennett Square PA 19348     Fax: 610-444-2420



> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden]On Behalf Of D. J. Raymond
> Sent: Friday, December 31, 1999 9:03 PM
> To: address@hidden
> Cc: address@hidden
> Subject: ugh!
>
>
> Here it is Y2K New Year's Eve and I could actually use some weather
> info with a storm coming in, and both my primary (Michigan) and backup
> (Northern Louisiana) ldm feeds are dead as a doornail!  Meanwhile our
> Debian Linux system + ldm continues to run without a blip.  What's
> going on?
>
> Dave Raymond
>