According to David Malone:
> We are supposed to contact the people running the pool and ask for
> a freebsd.pool.ntp.org subdomain.

That's a good idea.
 
> Second, we shouldn't have the local clock configured by default.

Why?

> The local clock should only be configured on a single server in a
> NTP domain that might be disconnected from the rest of the tree.
> Since the default config is a client config, it doesn't make sense
> to have the local clock configured. Even if it was a server config,
> it still wouldn't make sense, because it is only useful if a single
> server has it configured.

I do not see the point in removing it, it helps to keep the ntpd daemon
running if for some reason it loses the "real" ntp servers.

-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
In memoriam to Ondine : http://ondine.keltia.net/

_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Reply via email to