Re: ntpdate from cron -- DON'T DO THAT!

To: debian-user@lists.debian.org
Subject: Re: ntpdate from cron -- DON'T DO THAT!
From: John Hasler <john@dhh.gt.org>
Date: 21 Dec 2002 19:31:19 -0600
Message-id: <[🔎] 87lm2ix2jc.fsf@toncho.dhh.gt.org>
In-reply-to: <[🔎] 49785.10.10.10.7.1040518792.squirrel@webmail.linuxpowered.net>
References: <[🔎] 4.3.2.7.2.20021221104326.02875d18@nothnbut.net> <[🔎] 20021221235124.GC11323@cise.ufl.edu> <[🔎] 49172.10.10.10.7.1040516135.squirrel@webmail.linuxpowered.net> <[🔎] 20021222002820.GB2597@cise.ufl.edu> <[🔎] 49785.10.10.10.7.1040518792.squirrel@webmail.linuxpowered.net>

Nate writes:
> As above, only 1 system sync's to an external server, and it is a .gov
> server, time.nist.gov or something.

I was about to write that you should not use a stratum 1 server, but this
page <http://www.boulder.nist.gov/timefreq/service/its.htm> implies that
NIST doesn't mind at all.  I had planned to come up with a scheme for
chrony to distribute the load over the available stratum 2 servers, and
maybe even probe for one at your ISP and detect failure and pick a new
server.  Looks like I can just point them all at NIST.
-- 
John Hasler
john@dhh.gt.org (John Hasler)
Dancing Horse Hill
Elmwood, WI

Reply to:

References:
- ntpdate
  - From: Sonny Kupka <sonny@nothnbut.net>
- ntpdate from cron -- DON'T DO THAT!
  - From: "N. Thomas" <nthomas@cise.ufl.edu>
- Re: ntpdate from cron -- DON'T DO THAT!
  - From: "nate" <debian-user@aphroland.org>
- Re: ntpdate from cron -- DON'T DO THAT!
  - From: "N. Thomas" <nthomas@cise.ufl.edu>
- Re: ntpdate from cron -- DON'T DO THAT!
  - From: "nate" <debian-user@aphroland.org>

Prev by Date: Re: ntpdate from cron -- DON'T DO THAT! - more
Next by Date: Re: ntpdate from cron -- DON'T DO THAT!
Previous by thread: Re: ntpdate from cron -- DON'T DO THAT!
Next by thread: Re: ntpdate from cron -- DON'T DO THAT!
Index(es):
- Date
- Thread