Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)

To: debian-user@lists.debian.org
Subject: Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)
From: John Hasler <john@dhh.gt.org>
Date: 25 Dec 2002 16:03:58 -0600
Message-id: <[🔎] 87bs39lprl.fsf@toncho.dhh.gt.org>
In-reply-to: <[🔎] 20021222045743.GB16145@localhost>
References: <[🔎] 4.3.2.7.2.20021221104326.02875d18@nothnbut.net> <[🔎] 20021221235124.GC11323@cise.ufl.edu> <[🔎] 1040522180.7704.19.camel@pooh.honeypot.net> <[🔎] 20021222032330.GE2597@cise.ufl.edu> <[🔎] 3E0531FD.80E64036@helices.org> <[🔎] 874r96wv1z.fsf@toncho.dhh.gt.org> <[🔎] 20021222045743.GB16145@localhost>

> I thought chronyd did not implement all of the time protocol RFC and had
> fewer device interfaces for time sources.

AFAIK the only thing missing from Chrony is support for things like atomic
clocks.

> So, maybe in that sense ntpd is "technically the best"?

If you are running a stratum one server, yes.
-- 
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>
- This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)
  - From: Kirk Strauser <kirk@strauser.com>
- Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)
  - From: "N. Thomas" <nthomas@cise.ufl.edu>
- Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)
  - From: "Michael D. Schleif" <mds@helices.org>
- Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)
  - From: John Hasler <john@dhh.gt.org>
- Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)
  - From: "Eric G. Miller" <egm2@jps.net>

Prev by Date: Re: pon poff authority
Next by Date: Re: Strange behavior with APT::Default-Release
Previous by thread: Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)
Next by thread: Ntfs Problems
Index(es):
- Date
- Thread