Date: Thu, 8 Aug 2002 07:32:46 -0700 (PDT) From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Weird date in -CURRENT??!? Message-ID: <200208081432.g78EWk79009023@bunrab.catwhisker.org>
next in thread | raw e-mail | index | archive | help
I just noticed -- as the build machine was building the kernel for today's -CURRENT (while running -CURRENT from yesterday) that the datestamp on the kernel build messages looked odd: >>> Kernel build for FREEBEAST started on Sat Feb 19 07:02:37 PST 2011 >>> Kernel build for FREEBEAST completed on Sat Feb 19 07:22:18 PST 2011 Now, the same machine was running (today's) -STABLE when I did the "cvs update" in /usr/src: freebeast(5.0-C)[6] grep '^Script' current Script started on Thu Aug 8 05:35:01 2002 Script done on Thu Aug 8 05:48:52 2002 Script started on Sat Feb 19 05:52:10 2011 freebeast(5.0-C)[7] Now, looking at yesterday's build, I don't see that sort of anomalous behavior: freebeast(5.0-C)[7] grep '^Script' current.0 Script started on Wed Aug 7 05:30:58 2002 Script done on Wed Aug 7 05:41:28 2002 Script started on Wed Aug 7 05:44:36 2002 Script done on Wed Aug 7 07:21:27 2002 freebeast(5.0-C)[8] And note this: d144(4.6-S)[1] date && ssh freebeast date && date Thu Aug 8 07:22:52 PDT 2002 Sat Feb 19 07:22:24 PST 2011 Thu Aug 8 07:22:53 PDT 2002 d144(4.6-S)[2] In the mean time, I had cobbled up a dumb little program to spit out info from a timestamp (before "date" had format parameters that I knew of -- originally written on an IBM mainframe running MVS, about 1990 or so); anyway, it appears that the actual timestamp values are pretty far gone: d144(4.6-S)[2] tstamp && ssh freebeast tstamp && tstamp 1028816971 488268000 2002 220 08 08 4 07 29 31 488268000 August Thursday 0 1 31 PDT 1298129342 891857000 2011 050 02 19 6 07 29 02 891857000 February Saturday 0 0 28 PST 1028816973 096037000 2002 220 08 08 4 07 29 33 096037000 August Thursday 0 1 31 PDT d144(4.6-S)[3] (The leftmost output token is the raw "seconds since the epoch".) "freebeast" is the SMP build machine; d144 is one of the (uninspired) names assigned to DHCP clients on the wired net, and corresponds to the xe0 NIC that's in my laptop at the moment. (The latter machine is building today's -STABLE.) I'll see if I can figure something out after I boot up today's -CURRENT.... Cheers, david -- David H. Wolfskill david@catwhisker.org To paraphrase David Hilbert, there can be no conflicts between Microsoft and the discipline of systems administration, since they have nothing in common. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208081432.g78EWk79009023>