On Mon, Oct 05, 2020 at 03:16:24PM +0000, Roderick wrote: > > The result of time() has type time_t and we know what kind of number > goes there: seconds since 0 hours, 0 minutes, 0 seconds, January 1, > 1970, Coordinated Universal Time. > > In my FreeBSD running on a 64 bit processor this type is: int (__32_t). > It considers this size enough for above information. > > In my OpenBSD running on a 32 bit processor this type is: long long > (__64_t).
I hadn't looked in a while, but it amazes me that FreeBSD still has 32-bit time_t. > None of both has an unsigned type, although time moves forward > (more or less fast!!!). for precisely that reason, OpenBSD had completed the switch to 64-bit time_t by OpenSBD 5.5. Slides for Theo's 2013 keynote about that can be found here: http://www.openbsd.org/papers/eurobsdcon_2013_time_t/ (and I would not be terribly surprised to find that video exists out there somewhere too) - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
