also sprach Bill Moseley <[EMAIL PROTECTED]> [2002.12.05.0616 +0100]:
> This is on an old Dell PIII machine.
Speaking from experience, Dell PCs seem to be unable to keep the time
with any other operating system than Windoze. Do you have things like
Intel SpeedStep enabled in the BIOS?
I am using
A, the mist clears. That may be the source of my troubles some time back.
NTP _had_ been working flawlessly for many years, then all of a sudden it
stoped working properly on both of my machines. Exact symptoms that Bill is
describing.
Thinking back I had started using the ide-scsi on b
> >
>
>
> Weak CMOS battery?
No it's the system clock running slow, the hwclock actually seems to be
running a little *fast*. ;)
--
Bill Moseley [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bill Moseley wrote:
I setup a machine for a friend and every few days I ssh in to see how
things look. Twice now I have found the date about twenty minutes behind.
This is on an old Dell PIII machine.
Weak CMOS battery?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
[EMAIL PROTECTED] said:
> I also saw this problem on a suite of machines that were being used
> for distributed performance testing. We had xntpd running but the
> clocks still lost too much accuracy too quickly. We ended up setting
> up a process that automatically ran ntpdate every 10 seconds
tracked down the cause though.
-Original Message-
From: Bill Moseley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 11:19 PM
To: James Tappin; [EMAIL PROTECTED]
Subject: Re: Clock running slow
At 07:03 AM 12/05/02 +, James Tappin wrote:
>Does the machine have a S
At 07:03 AM 12/05/02 +, James Tappin wrote:
>Does the machine have a SCSI bus or a device running under ide-scsi? I
>have seen clocks run extremely slow (less than half speed) when using SCSI
>devices with disconnects disabled. NTP can fail to correct if the shift is
>too big.
Yes it does. Th
On Wed, 04 Dec 2002 21:16:23 -0800
Bill Moseley <[EMAIL PROTECTED]> wrote:
> I setup a machine for a friend and every few days I ssh in to see how
> things look. Twice now I have found the date about twenty minutes
> behind.
Does the machine have a SCSI bus or a device running under ide-scsi? I
At 04:51 PM 12/05/02 +1100, David Cureton wrote:
>I had this problem also, never really put my finger on what was causing it,
>however I have a feeling that is was due to the NTP server being a different
>NTP version.
>Running ntpdc utility:
> entering in the 'sysstats' command and observi
Bill Moseley wrote:
I setup a machine for a friend and every few days I ssh in to see how
things look. Twice now I have found the date about twenty minutes behind.
The first time I found this I ran ntpdate, made sure the hwclock was
updated, restarted ntp-simple and thought the problem was fixed.
hey guys,
out of curiosity, do you have errors in your /var/log/messages or syslog
about a missing char-major-10-135? i had the same problem on my machine
a while back because i didn't have rtc support in my kernel. just an
idea anyways. also, are you sure that you're connecting to the time
ser
I had this problem also, never really put my finger on what was causing it,
however I have a feeling that is was due to the NTP server being a different
NTP version.
Whilst there was nothing in the logs about this, the clue that lead me to
being different versions was that:
Running ntpdc util
I setup a machine for a friend and every few days I ssh in to see how
things look. Twice now I have found the date about twenty minutes behind.
The first time I found this I ran ntpdate, made sure the hwclock was
updated, restarted ntp-simple and thought the problem was fixed. I just
checked agai
13 matches
Mail list logo
