Comment 16 for bug 157608

Ok, let's pick this up again:

if I run "grep 'time reset' /var/log/ntpd" I get:
 5 Jun 17:43:58 ntpd[2769]: time reset +0.136732 s
11 Jun 11:18:39 ntpd[4993]: time reset +1.469716 s
12 Jun 10:56:34 ntpd[5080]: time reset +0.308096 s
15 Jun 13:22:48 ntpd[4957]: time reset +0.855029 s
17 Jun 10:27:13 ntpd[5171]: time reset +0.143075 s
18 Jun 09:56:47 ntpd[5104]: time reset +0.509730 s
26 Jun 09:56:58 ntpd[5026]: time reset +2.834653 s
27 Jun 10:03:12 ntpd[5131]: time reset +0.234493 s
30 Jun 09:39:08 ntpd[4896]: time reset +1.213153 s
 1 Jul 10:31:17 ntpd[5029]: time reset +0.789866 s
 3 Jul 04:34:55 ntpd[4950]: time reset +0.190097 s
 4 Jul 09:31:47 ntpd[5058]: time reset +0.180042 s
 7 Jul 09:54:03 ntpd[5029]: time reset +1.152314 s
 8 Jul 09:58:35 ntpd[5032]: time reset +0.316911 s

So my system does correct the clock... The only server I have under /etc/ntp.conf is ntp.ubuntu.com

However, in my log file I also have lines with "couldn't resolve `ntp.ubuntu.com', giving up on it", from what I can tell it's when I'm at home, so maybe my router is blocking the ntp packets...

I suggest that all add the "logfile /var/log/ntpd" line in /etc/ntp.conf, so we can have a better idea of what's going on...