From owner-freebsd-current@FreeBSD.ORG Tue Oct 12 14:55:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88A7716A505 for ; Tue, 12 Oct 2004 14:55:41 +0000 (GMT) Received: from web54008.mail.yahoo.com (web54008.mail.yahoo.com [206.190.36.232]) by mx1.FreeBSD.org (Postfix) with SMTP id C6E9A43D3F for ; Tue, 12 Oct 2004 14:55:28 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Message-ID: <20041012145528.12095.qmail@web54008.mail.yahoo.com> Received: from [147.46.44.181] by web54008.mail.yahoo.com via HTTP; Tue, 12 Oct 2004 07:55:28 PDT Date: Tue, 12 Oct 2004 07:55:28 -0700 (PDT) From: spam maps To: freebsd-current@freebsd.org In-Reply-To: <200410121536.41115.josemi@freebsd.jazztel.es> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: 5.3-Beta7 / router & ntpdate: bug in bootup script or sequence? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 14:55:42 -0000 --- Jose M Rodriguez wrote: > spam maps escribió: > > Hi, > > > > I have a router configured, which must properly > > synchronize time at bootup. For that purpose I > > use ntpdate to instantly adjust the time, then > > have let ntpd keep syncing time while running. > > All info for ntpdate and ntpd comes from > > /etc/ntp.conf. > > > > (ntpd also becomes the server of the local > > network, but that's now not so relevant) > > > > However, there seems to be something really odd > > when network access is needed for ntpdate; it > > simple cannot, and no time adjustment is done. > > > > Strangely enough: after bootup I can manually > > do the same ntpdate command, and it all works. > > > > Whatever I tried, nothing seems to help to get > > ntpdate do its work at bootup. My guess would > > be that there's something wrong with the bootup > > scripts or the sequence the scripts are called. > > > > The full bootup output, rc.conf and ntp.conf > > files are here: > > > > http://cisr.snu.ac.kr/ntpdate.txt > > > > I see this before. You are using named from here. > Seems it may have a race condition between named > and ntpdate. > > Try put an external nameserver on /etc/resolv.conf Even without named (named_enabled="NO"), and proper nameservers in /etc/resolv.conf, I get similar problems. See http://cisr.snu.ac.kr/ntpdate2.txt for the bootup process. I'm really puzzled why ntpdate is behaving so strange here. Is there a race condition between the network setup and ntpdate ? What makes it difficult to investigate, is that it only happens at bootup; after bootup, the ntpdate command works just fine! Yes, indeed I can avoid using ntpdate, but I believe there's something of a bootup bug here, which might be worthwhile finding.... Regards, Rob. _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com