Date: Mon, 8 Jul 1996 18:08:47 +0200 (MESZ) From: "Hr.Ladavac" <lada@ws2301.gud.siemens.co.at> To: lcurtis@intecom.com (Leon Curtis) Cc: questions@freebsd.org Subject: Re: Handling time after 1999 Message-ID: <199607081608.AA066302128@ws2301.gud.siemens.co.at> In-Reply-To: <Pine.BSD.3.93.960708085242.80A-100000@lcurtis.intecom.com> from "Leon Curtis" at Jul 8, 96 09:08:12 am
next in thread | previous in thread | raw e-mail | index | archive | help
In his e-mail Leon Curtis wrote: > I have been asked to look into what other unix kernel groups are planning > to do to address problems with time when the year 2000 arrives. Most probably nothing. AT&T based unices will have their D-day in 2038, sometime in January (when 32-bit time_t goes negative.) AFAIK, everyone who produced apps for unix internally encoded time as time_t (as it was easier.) Naturally, there will have been some poor souls who programmed in COBOL and used pic(99) for year, but then they deserved it. > > I would appreciate any pointers that would enable me to get "plugged in" > to any dialog / specifications relating to this issue. man time(2) gmtime(3) gettimeofday(2ucb) > > I work for a company that owns a version of (real time) unix put out > by LynxOS (Los Gatos, California). Our PBX product runs this OS and will > be the benefactor of the time changes. Are you sure your PBX product has been coded so that it's vulnerable? > > Thanks! /Marino
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607081608.AA066302128>