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. On Tue, Aug 17, 2010 at 10:34 AM, Jeremy <[email protected]> wrote: > I lost an hour on my workstation clock over the weekend, and 20 minutes > just over last night. ntpdate puts me right, but what is going on? Dying > CMOS battery? Is that even what keeps clock stable? System was on the > whole time, and running several VMs. > > Linux 2.6.32-24-generic #39-Ubuntu SMP x86_64 GNU/Linux > > Jeremy > _______________________________________________ > mlug mailing list > [email protected] > https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca >
_______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
