64bit time_t problem?

[Hiroki Sato]

Hi,

 I noticed that after the system clock set too far in the future,
 ntpdate could not reset it properly.  I tried the following (on 5.3-BETA1):

 # date 207008270000 ; ntpdate 192.168.100.1 ; date
 Wed Aug 27 00:00:00 JST 2070
 Looking for host 192.168.100.1 and service ntp
 host found : xxx.allbsd.org
 27 Aug 21:00:13 ntpdate[552]: step time server 192.168.100.1 offset -;0446744071497267106.746178 sec
 Fri Aug 27 21:00:13 JST 2004

 # date 210008270000 ; ntpdate 192.168.100.1 ; date
 Fri Aug 27 00:00:00 JST 2100
 Looking for host 192.168.100.1 and service ntp
 host found : xxx.allbsd.org
  4 Oct 03:26:57 ntpdate[521]: step time server 192.168.100.1 offset 1265599617.382757 sec
 Tue Oct  4 03:26:57 JST 2140

 # date 227008270000 ; ntpdate 192.168.100.1 ; date
 Password:
 Sat Aug 27 00:00:00 JST 2270
 Looking for host 192.168.100.1 and service ntp
 host found : xxx.allbsd.org
 10 Nov 09:57:37 ntpdate[564]: step time server 192.168.100.1 offset 195904656.965267 sec
 Fri Nov 10 09:57:37 JST 2276

 The time set by ntpdate has a period of about 136 years depending on
 the previous time.

 I think this is problematic because the system clock can go wrong
 when the box is left in a power-off state, for example.  Probably
 the time is handled in 32-bit somewhere, but I am not sure where it is.

 Is this a known problem or is there some workaround?

-- 
| Hiroki SATO
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20040827/8f5510ea/attachment.bin