Jobst Schmalenbach wrote, On 11/11/2010 07:41 PM:
> Hi.
>
> I run peridocally (from cron) on all of my machines
>
> 30 * * * * root /sbin/hwclock --systohc
>
Why?
AFAIK a kernel that is running ntpd and ntpd thinks has reasonably synced to
the NTP server will,
every _eleven_ minutes write th
On 11/11/2010 06:41 PM, Jobst Schmalenbach wrote:
> Hi.
>
> I run peridocally (from cron) on all of my machines
>
>30 * * * * root /sbin/hwclock --systohc
>
> All of those machines in question take their time via NTP
> from the same local server, and that server gets its time
> from a ntp pool.
Hi,
> On 11/14/10 5:38 PM, Jobst Schmalenbach wrote:
> > Ok I try that, but the thing is:
> >
> > * motherboards not that old
> > * its exactly 11 hours (+/- a couple of seconds) each time
>
>
> sounds like a conflict between time zones.a PC hardware clock could
> be set to UTC or local
On 11/14/10 5:38 PM, Jobst Schmalenbach wrote:
> Ok I try that, but the thing is:
>
> * motherboards not that old
> * its exactly 11 hours (+/- a couple of seconds) each time
sounds like a conflict between time zones.a PC hardware clock could
be set to UTC or local time. I always set my
On Thursday 11 November 2010 20:41:45 Jobst Schmalenbach wrote:
> Nov 10 08:08:52 XX ntpdate[2464]: step time server 192.168.1.1 offset
> -39599.950905 sec
Also, try to disable ntpdate with "chkconfig ntpdate off" and reboot the
machine
and see if that solves the problem. If it does, then yo
On Thursday 11 November 2010 20:41:45 Jobst Schmalenbach wrote:
> Now I had to reboot a couple of them two days ago and to my surprise
> all had problems with the time upon booting.
Hi,
Are you 100% sure that your timezone file (/etc/localtime) corresponds to the
one Australia/Melbourne? Try th
Ok I try that, but the thing is:
* motherboards not that old
* its exactly 11 hours (+/- a couple of seconds) each time
Jobst
On Fri, Nov 12, 2010 at 09:31:55AM -0500, Brunner, Brian T.
(bbrun...@gai-tronics.com) wrote:
>
> > and off course dovecot falls over too "Time just moved
> > bac
> 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?
I have this problem when dead batteries on the mobo prevent the hwclock
from preserving the t
Jobst Schmalenbach wrote:
Hi.
I run peridocally (from cron) on all of my machines
30 * * * * root /sbin/hwclock --systohc
All of those machines in question take their time via NTP
from the same local server, and that server gets its time
from a ntp pool.
Now I had to reboot a couple of them
On 11/11/2010 06:41 PM, Jobst Schmalenbach wrote:
> Hi.
>
> I run peridocally (from cron) on all of my machines
>
>30 * * * * root /sbin/hwclock --systohc
>
> All of those machines in question take their time via NTP
> from the same local server, and that server gets its time
> from a ntp pool.
Hi.
I run peridocally (from cron) on all of my machines
30 * * * * root /sbin/hwclock --systohc
All of those machines in question take their time via NTP
from the same local server, and that server gets its time
from a ntp pool.
Now I had to reboot a couple of them two days ago and to my surp
11 matches
Mail list logo
