On 08/17/2010 11:02 AM, Peter wrote: > running ntpdate just resets the time to a current value. > you want to run ntpd, which adjusts kernel parameters notices how it > ticks relative to a remote one, and over time speeds it up or slows it > down, whatever is appropriate. > > run ntpdate again, then try: > > sudo apt-get install ntp > > and, assuming it stays up and connected, it should stay synced after that. > Since the system learns (give it a few days) about how the clock > drifts, it will even stay better synced when it loses contact with > it's time sources for a few days, it won't just wander 10 minutes off > in a single day.
OK, but how do I keep time stable by itself? Is drift inevitable, and if so, why has it just happened recently. I do know about ntp and ntpdate, but since I don't need exact time all the time, the occasional ntpdate has always been fine. Jeremy _______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
