Joining NTP pool
Which leads me to my question. Would it be a waste of time (haw) to join the ntp pool if the UML host is already tweaking my clock? It might in fact be a bad idea to join the ntp pool since ntpd is probably assuming that no other agency is adjusting the system clock.
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.
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..
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".