From owner-freebsd-hackers  Thu Jun 22 21:47:36 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id VAA20553
          for hackers-outgoing; Thu, 22 Jun 1995 21:47:36 -0700
Received: from aries.ai.net (ai.net [198.69.35.206])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA20547
          for <hackers@FreeBSD.ORG>; Thu, 22 Jun 1995 21:47:33 -0700
Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id AAA15374; Fri, 23 Jun 1995 00:43:02 -0400
Date: Fri, 23 Jun 1995 00:43:02 -0400 (EDT)
From: Network Coordinator <nc@ai.net>
To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
cc: Mike Pritchard <mpp@legarto.minn.net>, hackers@FreeBSD.ORG
Subject: Re: Check the date and time at boot
In-Reply-To: <199506230055.RAA09076@gndrsh.aac.dev.com>
Message-ID: <Pine.BSF.3.91.950623004204.15185A-100000@aries.ai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@FreeBSD.ORG
Precedence: bulk

> 
> The more correct way to fix this is to use either ntpdate or timed
> at boot time.  Both are already supported by /etc/rc and /etc/sysconfig,
> I don't think we need yet a third way to get the date right during boot.
> 

Where should I look for a list of "good time hosts" [either timed or 
ntpdate] to sync a master time node to? I couldn't seem to get 
gatekeeper.dec.com to respond very well, but then again, that was also a 
shot in the dark.

Thanks,

-Jerry.