Bug#400390: [pkg-ntp-maintainers] Bug#400390: Please have ntp installed by default in the standard task

[Olaf van der Spek]

Kurt Roeckx wrote:
> On Sun, Nov 26, 2006 at 01:29:10PM +0100, Olaf van der Spek wrote:
>>> However, I'm not sure that the ntp is a package that should be installed
>>> by default, or atleast not run as a daemon by default.
>>>
>>> Something that runs ntpdate (or ntpd -q -g) regularly, or some sntp
>>> client, could make more sense for a default.
>> What are the advantages of ntpd or ntpdate?
> 
> I'm not sure what you're asking.
> 
> In the normal case you run ntpd as a daemon, it regularly sends packets
> out to synchronize the clock.  It will adjusts some kernel parameters
> so that your clock's rate is about correct.  It should get your clock
> accurate to a few ms.
> 
> If you run ntpdate (or ntpq -q) this is a one time only thing, and
> just adjusts to clock at that time, it won't do anything else.  This is
> basicly the sntp (simple ntp) behaviour, and you get a clock accurate
> in the order of a second.
> 
> If you run ntpd as a daemon, it acts as both client and server, it
> implements the full ntp protocol including all the algorithmes that go
> with it.
> 
> The problem with running ntpd default is that it's designed to act as
> an ntp server, and not to run on a desktop system or something that
> doesn't have a static IP address.

Why does it require a static IP address?
Better accuracy sounds desirable for desktops too.

> What you might want as a default installation is an sntp client.

In that case, shouldn't the Gnome clock panel also enable/disable sntp 
instead of ntp then?