In article <[EMAIL PROTECTED]>, Per Hedeland <[EMAIL PROTECTED]> wrote:
>And just to hopefully dispel some myths about *that*, i.e. Unix/POSIX
>time representation: First of all it really has nothing to do with NTP
>timestamps, but obviously ntpd needs to convert between the two. And it
>(currently) uses a 32-bit *signed* quantity for the seconds, with the
>value 0 in Jan 1970.
Depends on your operating system and platform. Viz.:
[EMAIL PROTECTED](5)$ cat >foo.c
#include <stdio.h>
#include <time.h>
int
main(void)
{
printf("sizeof(time_t) is %zu characters\n", sizeof(time_t));
}
[EMAIL PROTECTED](6)$ make foo
cc -O -pipe foo.c -o foo
[EMAIL PROTECTED](7)$ ./foo
sizeof(time_t) is 8 characters
[EMAIL PROTECTED](10)$ uname -sm
FreeBSD amd64
(As it turns out, FreeBSD is Y2038-ready on all 64-bit platforms.
Other operating systems will vary, and there may be other limitations
and sanity checks that prevent you from setting a particular date in
the far past or future.)
-GAWollman
--
Garrett A. Wollman | The real tragedy of human existence is not that we are
[EMAIL PROTECTED]| nasty by nature, but that a cruel structural asymmetry
Opinions not those | grants to rare events of meanness such power to shape
of MIT or CSAIL. | our history. - S.J. Gould, Ten Thousand Acts of Kindness
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
