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: 23 Dec 2002 08:09:41 -0600
Message-id: <[🔎] 87lm2grfmi.fsf@toncho.dhh.gt.org>
In-reply-to: <[🔎] 20021223111128.GH18705@mimar.dyndns.org>
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> <[🔎] 87ptrux3wq.fsf@toncho.dhh.gt.org> <[🔎] 20021223111128.GH18705@mimar.dyndns.org>

Chris Niekel writes:
> The NTP-docs mention that you should not use only one server, but more.

Is reliable time service of critical importance to you?  Most systems can
go for days without contacting a timeserver and suffer no harm.
-- 
John Hasler
john@dhh.gt.org (John Hasler)
Dancing Horse Hill
Elmwood, WI

Reply to:

Follow-Ups:
- Re: ntpdate from cron -- DON'T DO THAT!
  - From: Chris Niekel <chris@niekel.net>

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: John Hasler <john@dhh.gt.org>
- Re: ntpdate from cron -- DON'T DO THAT!
  - From: Chris Niekel <chris@niekel.net>

Prev by Date: Re: ntpdate from cron -- DON'T DO THAT!
Next by Date: Re: Slackware
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