Hi,
I’ve just setup a new OpenBSD 5.5 (snapshot) machine and noticed that svlogd logs all timestamps as such:
1900-01-00_00:00:00.95511
where the seconds never increment, only the 95511 portion will roll over and start back from zero, thus making svlogd’s timestamps useless. I’m running svlogd like this:
exec chpst -u svlog svlogd -tt ntp
I’m guessing that the problem might be related to the new implementation of time_t in OpenBSD:
http://www.openbsd.org/55.html
• time_t is now 64 bits on all platforms.
• From OpenBSD 5.5 onwards, OpenBSD is year 2038 ready and will run well beyond Tue Jan 19 03:14:07 2038 UTC.
• The entire source tree (kernel, libraries, and userland programs) has been carefully and comprehensively audited to support 64-bit time_t.
• Userland programs that were changed include arp(8), bgpd(8), calendar(8), cron(8), find(1), fsck_ffs(8), ifconfig(8), ksh(1), ld(1), ld.so(1), netstat(1), pfctl(8), ping(8), rtadvd(8), ssh(1),tar(1), tmux(1), top(1), and many others, including games!
• Removed time_t from network, on-disk, and database formats.
• Removed as many (time_t) casts as possible.
• Format strings were converted to use %lld and (long long) casts.
• Uses of timeval were converted to timespec where possible.
• Parts of the system that could not use 64-bit time_t were converted to use unsigned 32-bit instead, so they are good till the year 2106.
• Numerous ports throughout the ports tree received time_t fixes.
-mike
Received on Mon Apr 21 2014 - 19:18:18 UTC