[Freeipa-devel] ntp

[Simo Sorce]

On Fri, 2007-10-12 at 16:01 -0400, Karl MacMillan wrote:

> > It's not out of scope at all, we should do this for all clients anyway
> > like we configure kerberos and ldap.
> > The problem with ntp is that it seem that if it starts and it can't
> > contact the server it just dies. I have been told some times ago that
> > starting ntp with an empty configuration and piping in the right server
> > after it is started using a client tool provided in the package solves
> > this problem. Unfortunately it is too much for v1.
> > 
> 
> Since we don't have disconnected operation for v1 is this really an
> issue?

Yes it is, if your server start before your router/DNS/whatever makes it
not reach the ntp server, then, from what I have been told, your ntpd
will simply exit (no ntp for clients, kerberos breaks).

> > So for now we should just check ntp is up and running both on server and
> > client, and just *warn*. They maybe running something different that
> > keep clock in sync, we shouldn't force ntp at all costs.
> > 
> 
> Not certain what you mean - I think the server tools should setup an ntp
> server regardless. It doesn't hurt. The client tools should optionally
> configure ntp.

This is what I meant, more or less :)

Simo.