Date: Thu, 06 Jun 2002 21:08:17 -0400 From: Sergey Babkin <babkin@bellatlantic.net> To: Greg 'groggy' Lehey <grog@FreeBSD.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, John Baldwin <jhb@FreeBSD.org>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: src/etc/defaults rc.conf Message-ID: <3D000781.85795809@bellatlantic.net> References: <20020605084755.K91379@wantadilla.lemis.com> <50718.1023287177@critter.freebsd.dk> <20020606091023.B92654@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg 'groggy' Lehey wrote: > > On Wednesday, 5 June 2002 at 16:26:17 +0200, Poul-Henning Kamp wrote: > > In message <20020605084755.K91379@wantadilla.lemis.com>, "Greg 'groggy' Lehey" writes: > > > >>>> ntpdate(8) may be deprecated in the mind of the ntpd(8) author but > >>>> the replacement functionality isn't the same yet. > >>> > >>> If ntpdate is going away soon, we need to experiement with the > >>> replacement now. > >> > >> What's the replacement? > > > > Ideally, somebody would sit down and write a sntpd(8), which would be a > > light-weight, client-side-only NTP daemon without refclock support, > > without weird remote-configration stuff and other excess luggage. > > > > If somebody wants to volounteer, I will happily provide detailed > > guidance on the timekeeping magic needed. > > A good suggestion, but it misses the point. We shouldn't be throwing > out things like ntpdate *until* we have a replacement. And probably not even when we have a replacement. If it's functionality if available from ntpd with an option then ntpdate can be made a shell script calling ntpd but not completely thrown away. Ot's way too convenient to be thrown away. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D000781.85795809>