Bug 21692

Summary:	The time_t variable is only 4 bytes long
Product:	Base System	Reporter:	Wiktor NIESIOBÊDZKI <wn23590>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	1.0-RELEASE
Hardware:	Any
OS:	Any

Description Wiktor NIESIOBÊDZKI 2000-10-02 09:00:01 UTC

The time_t variable is only 4 bytes long, so for big values of it, strange behaviour can be expected

How-To-Repeat: 
root@patelnia:~# date
Sat Sep 30 11:35:55 CEST 2000
root@patelnia:~# date -r 2108591999
Sun Oct 26 01:59:59 CEST 2036
root@patelnia:~# date -r 2108592000
Sun Oct 26 01:00:00 CET 2036
Why the timezone has changed? 

root@patelnia:~# date -r 2147483647
Tue Jan 19 04:14:07 CET 2038
root@patelnia:~# date -r 2147483648
Fri Dec 13 22:09:52 WMT 1901
Do we need negative values of time_t?

Comment 1 Peter Wemm freebsd_committer

2000-10-02 20:02:43 UTC

Responsible Changed
From-To: gnats-admin->freebsd-bugs

misfiled PR

Comment 2 Poul-Henning Kamp freebsd_committer

2000-10-02 20:16:14 UTC

State Changed
From-To: open->closed

1. The timezone didn't change, but Daylight savings time ends in  
the last weekend of october in the CET timezone. 

2. It is far too early to decide what to do about time  
representation past 2038 at this time. 

3. If you have unique needed for time representation, you will need 
unique methods. 

4. A good guess is that we'll adopt a 64bit time_t sometime in the 
next five years (a 30 year margin seems likely).