Hi,I don't think so, because ntpd requires the local time setting of the system near by the time from the time-references servers. Otherwise it simply refuses to work. So it is required - at least in the current version of ntpd - to set the time to a value near by at least on time-reference server prior starting ntpd. This is done by ntpdate and ntpdate "normaly" extracts the set of relevant servers from ntp.conf. For external servers it is no good idea to use ip-addresses there, so named is required prior starting ntpdate.
As long as the ntpd in the ntpd-version off the NetBSD-distribution does not do the work of ntpdate during startup by itself, ntpdate is required. And at least in the case of a broadcast or multicast client I see a problem for ntpd to do it without additional information, that currently cannot be extracted from the ntp.conf file.
Best regards W. Stukenbrock Bernd Ernesti wrote:
The following reply was made to PR misc/44270; it has been noted by GNATS. From: Bernd Ernesti <netbsd%lists.veego.de@localhost> To: gnats-bugs%NetBSD.org@localhostCc: Subject: Re: misc/44270: startup order for ntpdate and named is broken in 5.1Date: Mon, 14 Feb 2011 20:18:20 +0100 Isn't ntpdate about to disapear which only leaves ntpd?Bernd
-- Dr. Nagler & Company GmbH Hauptstraße 9 92253 Schnaittenbach Tel. +49 9622/71 97-42 Fax +49 9622/71 97-50 Wolfgang.Stukenbrock%nagler-company.com@localhost http://www.nagler-company.com Hauptsitz: Schnaittenbach Handelregister: Amberg HRB Gerichtsstand: Amberg Steuernummer: 201/118/51825 USt.-ID-Nummer: DE 273143997 Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze