From owner-freebsd-questions  Fri Apr 25 21:08:04 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA03328
          for questions-outgoing; Fri, 25 Apr 1997 21:08:04 -0700 (PDT)
Received: from obie.softweyr.ml.org ([199.104.124.49])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03298
          for <questions@freebsd.org>; Fri, 25 Apr 1997 21:07:57 -0700 (PDT)
Received: (from wes@localhost) by obie.softweyr.ml.org (8.7.5/8.6.12) id VAA13638; Fri, 25 Apr 1997 21:14:35 -0600 (MDT)
Date: Fri, 25 Apr 1997 21:14:35 -0600 (MDT)
Message-Id: <199704260314.VAA13638@obie.softweyr.ml.org>
From: Wes Peters <softweyr@xmission.com>
To: Snob Art Genre <ben@narcissus.ml.org>
CC: questions@freebsd.org
Subject: Re: Year2000
In-Reply-To: <Pine.NEB.3.96.970423113048.25135A-100000@narcissus.ml.org>
References: <3.0.32.19970423201327.0073c33c@mail.hexanet.fr>
	<Pine.NEB.3.96.970423113048.25135A-100000@narcissus.ml.org>
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Christophe Prevotaux wrote:
 % Does FreeBSD passes the year2000 ?

Snob Art Genre writes:
 > Of course.  :)

FreeBSD does suffer from a problem shared by all other 32-bit
implementations of UNIX, however -- it's clock will "roll over"
someday.  The UNIX clock is implemented as a 32-bit signed integer
number of seconds since 00:00 Jan 1, 1970 GMT.  According to this simple
program:

#include <stdio.h>
#include <time.h>

main()
{
    time_t endEpoch = (time_t) 0x7fffffff;

    printf("Time ends at %s", ctime(&endEpoch));
}

Time ends at Mon Jan 18 20:14:07 2038.

This is in MST; your mileage may vary (+/- 12 hours).  The solution is,
of course, to move entirely to 64-bit processors before 2038.  I think
we'll handle this one.  ;^)

-- 
          "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                       Softweyr LLC
http://www.xmission.com/~softweyr                       softweyr@xmission.com