Re: Considering the removal of ntpdate
- To: debian-devel@lists.debian.org
- Subject: Re: Considering the removal of ntpdate
- From: Ron Johnson <ron.l.johnson@cox.net>
- Date: Tue, 21 Jul 2009 09:05:14 -0500
- Message-id: <[🔎] 4A65CB1A.5040708@cox.net>
- In-reply-to: <200904242053.04269.elendil@planet.nl>
- References: <200904231845.58928.petere@debian.org> <20090424180420.GB8431@paradigm.rfc822.org> <200904242049.35499.elendil@planet.nl> <200904242053.04269.elendil@planet.nl>
On 2009-04-24 13:53, Frans Pop wrote:
On Friday 24 April 2009, Frans Pop wrote:
Florian Lohoff wrote:
rdate ist not a replacement for ntpdate - it does not use the ntp
protocol but the time protocol (builtin inetd) - So making
ntpdate depend on rdate is not a solution as it changes the protocol
and i dont think all ntp servers also open/support the time protocol.
rdate also supports the ntp protocol. From the man page:
-n Use SNTP (RFC 2030) instead of the RFC 868 time protocol.
And JFYI, since Lenny Debian Installer uses rdate to update the system
time during installs (rdate -o 123 -nvv "$server") and we've not seen any
issues with that.
Something seems seriously wrong with rdate, or how I'm using it...
# rdate -ncv -p -o 123 ntp.cox.net
Tue Jul 21 08:52:29 CDT 2009
rdate: adjust local clock by 24.000529 seconds
# ntpdate -q ntp.cox.net
server 68.0.14.76, stratum 1, offset 0.000138, delay 0.06146
21 Jul 08:54:40 ntpdate[5494]: adjust time server 68.0.14.76
offset 0.000138 sec
--
Scooty Puff, Sr
The Doom-Bringer
Reply to: