On Fri, Feb 25, 2005 at 01:17:27AM +0100, Wouter Verhelst wrote: > On Fri, Feb 25, 2005 at 10:18:00AM +1100, Drew Parsons wrote: > > Is there a problem with the clock on the m68k buildd? > > Uh, "the"? There are eleven of them ;-) > > > I uploaded gworldclock 1.4.2 yesterday, and the m68k buildd reports: > > > > make[3]: Warning: File `rendezvous.c' has modification time 1.6e+04 s in > > the future > > ... > > make[3]: warning: Clock skew detected. Your build may be incomplete. > > > > No other architecture gave the same warning, and the file date itself is > > 2005-02-24 20:16, which I can compare to timer.c's date, 2005-02-24 > > 23:45 (3.5 hours later, with no make warning). > > Looks like it, yes. > > Christian: what kind of machine is chya? Are you running ntpdate from > cron? Is the nvram battery still good?
Talking to me? That is not my box, no idea what it is. I had this on my mac a couple of times, but I am running ntp on all my boxes nowadays. Maybe the crest page should be updated to show all "11" machines, perhaps we halve 12 already? Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
