From owner-freebsd-current@FreeBSD.ORG  Tue Oct 12 13:16:55 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 9595B16A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 12 Oct 2004 13:16:53 +0000 (GMT)
Received: from web54007.mail.yahoo.com (web54007.mail.yahoo.com
	[206.190.36.231])
	by mx1.FreeBSD.org (Postfix) with SMTP id 141A643D3F
	for <freebsd-current@freebsd.org>;
	Tue, 12 Oct 2004 13:16:53 +0000 (GMT)
	(envelope-from spamrefuse@yahoo.com)
Message-ID: <20041012131652.33782.qmail@web54007.mail.yahoo.com>
Received: from [147.46.44.181] by web54007.mail.yahoo.com via HTTP;
	Tue, 12 Oct 2004 06:16:52 PDT
Date: Tue, 12 Oct 2004 06:16:52 -0700 (PDT)
From: spam maps <spamrefuse@yahoo.com>
To: freebsd-current <freebsd-current@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2004 13:16:55 -0000


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 hope this may give an idea what is going wrong
here.

Thanks,
Rob.


	
		
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail