Displaying 1 result from an estimated 1 matches for "39600s".
Did you mean:
3600s
2010 Nov 12
7
hwclock problem
...X ntpdate[2464]: step time server 192.168.1.1 offset -39599.950905 sec
Nov 10 08:08:52 XXXXXX xinetd[2447]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
and off course dovecot falls over too "Time just moved backwards by 39599 seconds."
Now, 39600s is 11 hours, which is (inc DST) *MY* offset from Greenwich.
So what am I doing wrong?
The idea of running hwclock is to make sure that exactly the problem with dovecot does NOT occur, and ntp does not have a coughing fit when the hardware clock is not close to the correct time upon booting.
The l...