[pkg-ntp-maintainers] Bug#484974: Bug#484974: Bug#484974: ntpdate's ip-up script runs even for virtual interfaces

[Josip Rodin]

(Please note that mailing <nnn>@bugs doesn't reach the bug submitter.
I only saw this after a manual lookup.)

On Wed, Jun 18, 2008 at 10:18:24PM -0400, Steve Kostecke wrote:
> Peter Eisentraut said:
> 
> >What are you using ntpdate for?
> 
> A better question is why are you using ntpdate at all?
> 
> Besides the diagnostics that ntpdate can produce, the only advantage
> ntpdate has over ntpd is that ntpdate can use an unpriviledged source
> port and ntpd currently can not.
> 
> ntpd can perform an unlimited step to set the clock if you start it with
> '-g'.
> 
> ntpd can emulate ntpdate and even block the boot sequence if started
> with '-gq'
> 
> In tests on my LAN 'ntpd -gq' can set the clock (or start the slew) and
> exit in ~11 seconds

I answered this earlier, but here goes one more time: I use ntpdate for its
exact simplest purpose - setting the clock ad hoc from a specified NTP
server. The machine doesn't have ntpd installed, and I either don't want
it at all, or I don't want ntpd but openntpd on it.

> FWIW, ntpdate is deprecated upstream ...

Well, if that's supposed to mean that you don't want to maintain it because
of that, then I can only suggest that nobody's forcing you to do it...
also, nobody's forcing you to make random changes which "seem like
a useful generalization", but aren't necessarily...

-- 
     2. That which causes joy or happiness.