Joining NTP pool

The linode server is time sync'd and, by default, your own linode will follow the server clock so there is no need to run ntp on your linode.

I think the question here is whether or not he should run an ntp server, so that other people can grab ntp data from him.

I would personally suggest that this wouldn't be a good idea. Since it's synced up already by the host, you don't know what it's synced to, so you can't yourself vouch for the accuracy of that source. Furthermore, you don't know how many hops you are from a known good time source, although you could always ask, I guess. :)

Well i added my two servers to the pool yesterday..

They do checking to see how out of date ur server is etc so.. if your host was out i assume you would find out pretty quickly..

I agree with Ciaran, the fact that you don't have a solid reference for your NTP server makes it a bad choice to add to the ntp pool project.

Think about it:

• at what stratum are you running?

• what are you presenting as an upstream reference?

The whole idea behind NTP is that you have a traceable upstream source and the ntp client can make informed decisions about accuracy. With a linode you're dependant on the host's clock and you have no idea if it's synched, or to what stratum is synched. In exactly the same way, the client also cannot root out "bad tickers".

–deckert