Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 84EFA9FBB6A for ; Mon, 16 Jul 2007 21:39:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 10160-01 for ; Mon, 16 Jul 2007 21:39:22 -0300 (ADT) Received: from hub.org (hub.org [200.46.204.220]) by postgresql.org (Postfix) with ESMTP id 2A7F09FBA79 for ; Mon, 16 Jul 2007 21:39:49 -0300 (ADT) Received: from localhost (maia-4.hub.org [200.46.204.183]) by hub.org (Postfix) with ESMTP id 2113AB46DD1 for ; Mon, 16 Jul 2007 21:39:49 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 78948-02; Mon, 16 Jul 2007 21:39:32 -0300 (ADT) Received: from ganymede.hub.org (blk-89-241-126.eastlink.ca [24.89.241.126]) by hub.org (Postfix) with ESMTP id 77523B46DB1; Mon, 16 Jul 2007 21:39:42 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id D35448CBAB; Mon, 16 Jul 2007 21:39:36 -0300 (ADT) Date: Mon, 16 Jul 2007 21:39:36 -0300 From: "Marc G. Fournier" To: Tom Lane cc: pgsql-www@postgreSQL.org Subject: Re: Clock skew with PG CVS repository? Message-ID: <7E6D2000E82D99E3D740A3B9@ganymede.hub.org> In-Reply-To: <20331.1184620669@sss.pgh.pa.us> References: <20331.1184620669@sss.pgh.pa.us> X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/17 X-Sequence-Number: 12164 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Monday, July 16, 2007 17:17:49 -0400 Tom Lane wrote: > I've noted a couple of cases recently that seem to indicate the CVS > machine's clock is a few seconds ahead of mine, eg just now I did > "cvs commit" and then immediately "make", and got this: > > $ make > make: *** Warning: File `lock.c' has modification time in the future > (2007-07-16 17:09:50 > 2007-07-16 17:09:43) gcc -O1 -Wall > -Wmissing-prototypes -Wpointer-arith -Winline -fno-strict-aliasing -g > -I../../../../src/include -D_XOPEN_SOURCE_EXTENDED -c -o lock.o lock.c gcc > -O1 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -fno-strict-aliasing > -g -I../../../../src/include -D_XOPEN_SOURCE_EXTENDED -c -o proc.o proc.c > /usr/ccs/bin/ld -r -o SUBSYS.o lmgr.o lock.o proc.o deadlock.o lwlock.o > spin.o s_lock.o make: warning: Clock skew detected. Your build may be > incomplete. > $ > > Manually issuing "date" on cvs.postgresql.org seems to confirm it's > about ten seconds fast compared to here. Now NTP swears up and down > that I'm synced within a few milliseconds of three different reference > machines, so I think the problem is at that end. Is cvs.postgresql.org > supposed to be running NTP? 'Cause I don't see any such daemon there. > > I haven't noticed this type of problem before, so your machine usually > keeps good time, but right now it isn't. Looking into it ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGnA/I4QvfyHIvDvMRAn6+AJ9kdJ6c+UKyRgBdXVSROpbH4as38ACgiwXk Qc5Hku2Y32HRrU0xJr1m6Vo= =LYoE -----END PGP SIGNATURE-----