On Apr 11, 10:49=A0am, rott <richard.ottin...@[EMAIL PROTECTED]
> wrote:
> On Apr 11, 11:19 am, dbenedic...@[EMAIL PROTECTED]
wrote:
>
>
>
>
>
> > On Apr 11, 8:30 am, rott <richard.ottin...@[EMAIL PROTECTED]
> wrote:
>
> > > I'm having a problem getting d3 andlinuxtime values to match and to
> > > stay matched.
>
> > > For example: currentlinuxtime=3D10:30AM
> > > I do a tcl command...set-time10:30:00 (u
>
> > > I then verify that both time values match...then next day I do a tcl
> > > command... time & d3 time is exactly one hour behindlinux
> > > time....linuxtime is right...d3 time is wrong
>
> > > I am using ntp.
>
> > > Thanks,
> > > Richard
>
> > Someone correct me if I'm wrong!
>
> > I don't believe that the time in D3 uses theLinuxor the real time
> > clock on the motherboard to keep time. =A0It does get the time when
> > booting up. =A0After that I beleive that the time is kept by D3
itself,
> > as you can set the time in D3 to anything you wish.
>
> > That being said, I have seen problems with D3 and earlier versions of
> > AP and AP/Pro that had a hard time getting the correct clock ticks
> > from the motherboard, and thereby lose track of the time.
>
> > If no one else comes up with a fix, you may want to start a background
> > job that resets the time in D3 every hour or so.
>
> > Regards,
>
> > Dale
>
> Hello Dale,
> I am using D3/Linux 7.5.0. =A0I have not rebooted d3 or linux since I
> changed the time using the set-time tcl command... d3 time just
> changed itself automatically. =A0d3 time is now exactly an hour behind
> linux time. =A0linux time is correct.
> Thanks
> Richard- Hide quoted text -
>
> - Show quoted text -
Is the time always out by exactly one hour? Or does the system
gradually, lose the hour over the day?
Check the error logs (list-errors), the system normally captures time
changes. Maybe someone else is changing the time.
Regards,
Dale
|
