On 16 February 2010 20:57, Andy Smith <andy@???> wrote:
>> Feb 16 20:00:37 calliope ntpd[1187]: synchronized to 213.132.202.192, stratum 2
>
> You're now synced to an NTP server and have the correct time. Does
> it later lose sync?
Hello Andy,
No, as far as I can see, it's only the initial boot that starts 30
mins out. Once we sync, we're OK.
> Is it possible that what you describe as an "OK" boot had
> independent_wallclock set to 0 so you were unable to set the time,
> it remained wrong, and dovecot did not complain? Personally I would
> rather have the right time and make dovecot start after ntpdate.
No - the "bad" boot was always the time jumping 30 mins - the time has
always ended up correct after boot, just sometimes needing the large
adjustment. which sometimes makes Dovecot die.
> Having it boot with the wrong time and then have ntpdate/ntp adjust
> it is the best I can offer I'm afraid, because that's the best I've
> been able to achieve.
That's fine.
I am OK if I can find a setting that ends up with the right time
(whether we start right or need a large adjustment) and doesn't cause
Dovecot to die. I think I can get to this state (if I am not already).
Just odd - sometimes 30 mins out at start, sometimes not.
> kahlua$ sudo hwclock --systohc && date && hwclock --show
> Password:
> Tue Feb 16 20:51:53 UTC 2010
> Tue 16 Feb 2010 20:51:54 UTC -0.472518 seconds
>
> Does that change things?
I'll do some more tests tomorrow and report back anything of interest.
Thanks for the help.
Cheers,
--
Alastair Sherringham
