Date: Mon, 19 May 2008 13:31:13 -0500 From: Dave Uhring <duhring@charter.net> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-stable@freebsd.org Subject: Re: Buildworld Fails RELENG_7 Message-ID: <20080519183113.GA55295@charter.net> In-Reply-To: <20080519180028.GA79392@eos.sc1.parodius.com> References: <20080519151739.GA50653@charter.net> <4AB77C7C-55F7-4CC3-B842-E684F6C899E3@rabson.org> <20080519163825.GA32372@charter.net> <DB8B754A-5994-4358-9F8C-93218AAEF9F4@rabson.org> <20080519165421.GA62264@charter.net> <20080519165925.GA77907@eos.sc1.parodius.com> <20080519170334.GA74159@charter.net> <20080519170619.GC77907@eos.sc1.parodius.com> <20080519180028.GA79392@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 19, 2008 at 11:00:28AM -0700, Jeremy Chadwick wrote: > > Something I thought of while doing the above: there's been reports in > the past of problems with buildworld (or building software in general) > bombing out or behaving oddly due to clock issues on the local machine. > If you don't use ntpd, consider doing so. Otherwise, at least use > ntpdate once to set your clock to something sane. I hadn't yet started ntpd but [root@maxwell /etc]# ntpdate newton 19 May 13:29:22 ntpdate[55524]: step time server 192.168.0.8 offset -1.044724 sec I doubt that a second off would make any difference.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080519183113.GA55295>