After running NTPD on VxWorks for a couple days, the ntp.drift file
was set to -500, that made it jump to the infinite loop trying to call
adjtime(), but VxWorks doesn't have adjtime().
I read the ntp documentation. It suggests to disable the time-of-year
(TOY) clock chip. How do I disable this cl
Aggie wrote:
> After running NTPD on VxWorks for a couple days, the ntp.drift file
> was set to -500, that made it jump to the infinite loop trying to call
> adjtime(), but VxWorks doesn't have adjtime().
>
> I read the ntp documentation. It suggests to disable the time-of-year
> (TOY) clock chip.
Aggie wrote:
> After running NTPD on VxWorks for a couple days, the ntp.drift file
> was set to -500, that made it jump to the infinite loop trying to call
> adjtime(), but VxWorks doesn't have adjtime().
>
> I read the ntp documentation. It suggests to disable the time-of-year
> (TOY) clock chip.
I don't know how much it lose/gain per day yet. I will run it
overnight today. If it is indeed a hardware problem, how can I fix it?
If it is not, what other problem may it be? I saw someone in the forum
who could resolve this problem by changing the HZ varilable in the
kernel to 250. But his origi
On Nov 26, 10:54 pm, "David J Taylor" <[EMAIL PROTECTED]
this-bit.nor-this-bit.co.uk> wrote:
> Aggie wrote:
> > After running NTPD on VxWorks for a couple days, the ntp.drift file
> > was set to -500, that made it jump to the infinite loop trying to call
> > adjtime(), but VxWorks doesn't have adjt
Aggie wrote:
> I don't know how much it lose/gain per day yet. I will run it
> overnight today. If it is indeed a hardware problem, how can I fix it?
If the hardware is under warranty, you ask the vendor to fix it! If
not, you have a problem! If it's a PC more than three years old,
consider re
On 2007-11-27, Aggie <[EMAIL PROTECTED]> wrote:
> On Nov 26, 10:54 pm, "David J Taylor" wrote:
>
>> Delete the drift file??
>
> Did you leave ntp running when [you] deleted the drift file or did you
> restart ntp after [you] delete the drift file?
Restart ntpd after deleting the drift file.
This
Aggie wrote:
[]
> Did you leave ntp running when u deleted the drift file or did you
> restart ntp after u delete the drift file?
>
>> near correct value??
> What is a near correct value?? How do I find out what's the correct
> value for my hardware?
>
>> Of course, as Richard says, it could be a h
On 2007-11-27, Aggie <[EMAIL PROTECTED]> wrote:
> I don't know how much it lose/gain per day yet. I will run it
> overnight today. If it is indeed a hardware problem, how can I fix it?
The frantically shouted phrase "hardware problem!" can, in reality,
refer to a wide range of issues.
If your c
>Restart ntpd after deleting the drift file.
I think some version of ndpd used to write out the drift file
when it exited. (Maybe I'm dreaming and that was just a
suggestion for purposes of discussion.)
So I would do
stop ntpd
delete the drift file
start ntpd
Then you know it got deleted
Hal Murray wrote:
>> Restart ntpd after deleting the drift file.
>
> I think some version of ndpd used to write out the drift file
> when it exited. (Maybe I'm dreaming and that was just a
> suggestion for purposes of discussion.)
>
> So I would do
> stop ntpd
> delete the drift file
> sta
On 2007-11-28, Tom Smith <[EMAIL PROTECTED]> wrote:
> Yes. And one missing step:
>
> After stopping ntpd, "ntpdate -b [server]".
ntpdate is deprecated and no longer maintained.
'ntpq -gq' is the suggested replacement using ntpd.
--
Steve Kostecke <[EMAIL PROTECTED]>
NTP Public Services Project
Steve Kostecke wrote:
> On 2007-11-28, Tom Smith <[EMAIL PROTECTED]> wrote:
>
>> Yes. And one missing step:
>>
>> After stopping ntpd, "ntpdate -b [server]".
>
> ntpdate is deprecated and no longer maintained.
>
> 'ntpq -gq' is the suggested replacement using ntpd.
>
And wait until it finishes
On 2007-11-28, Tom Smith <[EMAIL PROTECTED]> wrote:
> Steve Kostecke wrote:
>
>> On 2007-11-28, Tom Smith <[EMAIL PROTECTED]> wrote:
>>
>> ntpdate is deprecated and no longer maintained.
>>
>> 'ntpq -gq' is the suggested replacement using ntpd.
>
> And wait until it finishes, of course.
# time nt
Steve Kostecke wrote:
> On 2007-11-28, Tom Smith <[EMAIL PROTECTED]> wrote:
>
>> Steve Kostecke wrote:
>>
>>> On 2007-11-28, Tom Smith <[EMAIL PROTECTED]> wrote:
>>>
>>> ntpdate is deprecated and no longer maintained.
>>>
>>> 'ntpq -gq' is the suggested replacement using ntpd.
>> And wait until it
David,
> What happens if you delete the drift file and leave it for a few hours?
After I deleted the drift file and left it run overnight, the drift
file was not created in the first couple hours and when I checked this
morning. ntp.drift and ntp.drift.TEMP were created. ntp.drift couldn't
be open
Richard.
> If the hardware is under warranty, you ask the vendor to fix it! If
> not, you have a problem! If it's a PC more than three years old,
> consider replacing it! PCs will usually last a lot longer than three
> years but technology moves so fast that three years is almost synonymous
> w
Steve,
> Restart ntpd after deleting the drift file.
I did that. But when I ran it overnight, the drift file with 500 was
created, (but the ntp was still running). Last time when I ran it for
3 days, the drift file had a value of -500 in the end, and ntp had
stopped sync-ing the clock on the clie
Aggie wrote:
> David,
>> What happens if you delete the drift file and leave it for a few
>> hours?
>
> After I deleted the drift file and left it run overnight, the drift
> file was not created in the first couple hours and when I checked this
> morning. ntp.drift and ntp.drift.TEMP were created.
David,
> That sounds like a permissions error. I did see something similar in
> Windows some time back. On Windows, at least, you can read the ntp.drift
> file almost any time.
Thank you very much. But I don't think it is a permission error,
because I'm using "target server" thing which allow m
Kev,
Do I recall you said you were using HZ=60? If so, I recommend trying HZ=100
instead.
If you look at your logfile output, are you seeing time steps of
approximately the same amount at approximately the same time intervals?
If not, you probably have interrupt or BIOS or some other external p
Much easier still, forget about the initial set and just add -g to the flag
list when starting ntpd.
If you need to have the clock in a "stable/sync'd" state before starting
certain other servers, put a call to ntp-wait just before you want the
sensitive processes started.
H
Aggie wrote:
> David,
>
>> That sounds like a permissions error. I did see something similar in
>> Windows some time back. On Windows, at least, you can read the
>> ntp.drift file almost any time.
>
> Thank you very much. But I don't think it is a permission error,
> because I'm using "target ser
Harlan,
I have been usign the -g option everytime i run ntpd.
> Do I recall you said you were using HZ=60? If so, I recommend trying HZ=100
> instead.
Ok, I will try that tomorrow. I'm testing how many second I gain
without runninig ntpd. Btw, what is the HZ for? what does it do?
> If you loo
Aggie wrote:
> David,
>> What happens if you delete the drift file and leave it for a few hours?
>
> After I deleted the drift file and left it run overnight, the drift
> file was not created in the first couple hours and when I checked this
> morning. ntp.drift and ntp.drift.TEMP were created. nt
>I don't think it's a hardware product defect. Because we have two of
>them, and we had run the same test on both of the board, we still got
>the same error. Thanks,
There are two kinds of hardware (or software) errors. One is a design
error. The problem happens all the time on all units. The
Aggie,
Aggie wrote:
> Harlan,
>
> I have been usign the -g option everytime i run ntpd.
This is only to allow a large initial time offset to be accepted by ntpd.
Normally ntpd stops itself if the time offset exceeds ~1000 seconds, and
adds a warning to the syslog saying you should first set the
I think I found out where the problem is.
VxWorks doesn't have adjtime( ), and the one we wrote wasn't doing
anything. That's what makes the drift to increase to +500 (I think).
Does that make sense??
We would like to know what adjtime( ) actually does, so we can rewrite
it for VxWorks correctly.
Aggie wrote:
> I think I found out where the problem is.
>
> VxWorks doesn't have adjtime( ), and the one we wrote wasn't doing
> anything. That's what makes the drift to increase to +500 (I think).
> Does that make sense??
>
> We would like to know what adjtime( ) actually does, so we can rewrit
Aggie wrote:
> Harlan,
>
> I changed hz to 100 and ran it overnight yesterday. It seemed like it
> had affect on the drift file problem, because normally the drift file
> would have already been created after 10 hrs, and complained about 500
> value in the drift file. But now the drift file still
Aggie wrote:
> Harlan,
>
> I changed hz to 100 and ran it overnight yesterday. It seemed like it
> had affect on the drift file problem, because normally the drift file
> would have already been created after 10 hrs, and complained about 500
> value in the drift file. But now the drift file still h
Harlan,
I changed hz to 100 and ran it overnight yesterday. It seemed like it
had affect on the drift file problem, because normally the drift file
would have already been created after 10 hrs, and complained about 500
value in the drift file. But now the drift file still has not been
created yet,
>>> In article <[EMAIL PROTECTED]>, Aggie <[EMAIL PROTECTED]> writes:
Aggie> Harlan, I changed hz to 100 and ran it overnight yesterday. It seemed
Aggie> like it had affect on the drift file problem, because normally the
Aggie> drift file would have already been created after 10 hrs, and
Aggie> co
>>> In article <[EMAIL PROTECTED]>, Aggie <[EMAIL PROTECTED]> writes:
Aggie> I think I found out where the problem is. VxWorks doesn't have
Aggie> adjtime( ), and the one we wrote wasn't doing anything. That's what
Aggie> makes the drift to increase to +500 (I think). Does that make
Aggie> sense
>Yes. And one missing step:
>
>After stopping ntpd, "ntpdate -b [server]".
>
>The single most common cause of a large negative drift value
>is a system whose clock has not been initialized before starting
>ntpd (or has been stopped during a large time adjustment).
What vintage of ntpd are you usi
Aggie wrote:
> I think I found out where the problem is.
>
> VxWorks doesn't have adjtime( ), and the one we wrote wasn't doing
> anything. That's what makes the drift to increase to +500 (I think).
> Does that make sense??
>
> We would like to know what adjtime( ) actually does, so we can rewrit
Hal Murray wrote:
>> Yes. And one missing step:
>>
>> After stopping ntpd, "ntpdate -b [server]".
>>
>> The single most common cause of a large negative drift value
>> is a system whose clock has not been initialized before starting
>> ntpd (or has been stopped during a large time adjustment).
>
>
On Nov 30, 11:24 pm, Harlan Stenn <[EMAIL PROTECTED]> wrote:
> >>> In article <[EMAIL PROTECTED]>, Aggie <[EMAIL PROTECTED]> writes:
>
> Aggie> I think I found out where the problem is. VxWorks doesn't have
> Aggie> adjtime( ), and the one we wrote wasn't doing anything. That's what
> Aggie> makes
38 matches
Mail list logo
