Hello,<br><br>I have just upgraded my VM from etch to lenny, and things look good overall.<br><br>One annoyance however is that on a reboot, the clock is ~30 mins in the future and this is only fixed by a CRON @reboot job of &quot;ntpdate&quot;, which adjusts this correctly (offset -1935.350400 sec). However, this large adjustment causes dovecot to kill itself.<br>
<br>On boot (via console) I can see :<br><br>..<br>drivers/rtc/hctosys.c: unable to open rtc device (rtc0)<br>..<br>Waiting for /dev to be fully populated...done.<br>Setting the system clock.<br>Unable to set System Clock to: Thu Jan 21 15:01:46 UTC 2010 (warning).<br>
..<br>Setting the system clock.<br>Unable to set System Clock to: Thu Jan 21 15:01:49 UTC 2010 (warning).<br>Cleaning up ifupdown....<br>...<br><br>This is using lenny kernel 2.6.26-2-xen-686.<br><br>I tried setting &quot;xen.independent_wallclock = 1&quot; in /etc/sysctl.conf but this does not make a difference.<br>
<br>hwclock --show<br><br>returns nothing.<br><br>Any idea why the clock needs such a large adjustment on reboot?<br><br>Cheers,<br><br clear="all"><br>-- <br>Alastair Sherringham<br><br>