Here's what I want to do:
To have NTPD run on VxWorks and Windows. Set VxWorks as the Server
and Windows as the Client. My Ulitmate goal is the sync these two
clocks.
Here's the scenario:
Whenever I power cycle VxWorks, it will set the clock to 00:00, Jan
1, 1970. It's default. I wrote a simpl
Aggie wrote:
> Here's what I want to do:
> To have NTPD run on VxWorks and Windows. Set VxWorks as the Server
> and Windows as the Client. My Ulitmate goal is the sync these two
> clocks.
>
> Here's the scenario:
> Whenever I power cycle VxWorks, it will set the clock to 00:00, Jan
> 1, 1970.
In article <[EMAIL PROTECTED]>,
Aggie <[EMAIL PROTECTED]> wrote:
> To have NTPD run on VxWorks and Windows. Set VxWorks as the Server
> couple minutes, the clock on Windows was changed to 5:15pm, Nov 21
> 1988. I have no idea why it happened. So I looked at the timestamp
> Reference clock upda
On Oct 30, 4:01 pm, [EMAIL PROTECTED] (David
Woolley) wrote:
> In article <[EMAIL PROTECTED]>,
>
> Aggie <[EMAIL PROTECTED]> wrote:
> > To have NTPD run on VxWorks and Windows. Set VxWorks as the Server
> > couple minutes, the clock on Windows was changed to 5:15pm, Nov 21
> > 1988. I have no ide
Aggie wrote:
[]
> But the weird thing is: NTPD will adjust the time on the client half
> way between the server and 1970 Jan 1. For example, if the clock on my
> server is in 2000, then the clock on the client will be set to 1985.
> I have no idea what's going on. Any input would help.
>
> Kevin
P
In article <[EMAIL PROTECTED]>,
Aggie <[EMAIL PROTECTED]> wrote:
> But the weird thing is: NTPD will adjust the time on the client half
> way between the server and 1970 Jan 1. For example, if the clock on my
What is weird is that the reply from your server is accepted. Once it
is accepted, near
In article <[EMAIL PROTECTED]>,
Aggie <[EMAIL PROTECTED]> wrote:
> But the weird thing is: NTPD will adjust the time on the client half
> way between the server and 1970 Jan 1. For example, if the clock on my
PS. Unless you have explicitly disabled the feature, either for the first
setting, or u
David Woolley wrote:
> In article <[EMAIL PROTECTED]>,
> Aggie <[EMAIL PROTECTED]> wrote:
>
>> But the weird thing is: NTPD will adjust the time on the client half
>> way between the server and 1970 Jan 1. For example, if the clock on my
>
> PS. Unless you have explicitly disabled the feature,
Brian:
Yes, ntpd wasn't run until after the clock change.
David:
I'm using ntp-dev-4.2.5p83.tar.gz
David:
I'm using option -g, so i can step more than 1000s.
Dear all,
I modified the ntp_io.c and undefine HAVE_TIMESTAMP and
USE_TIMESTAMP_CMSG by adding #if 0, like the following:
/*#if defined(
David,
Martin Burnicki wrote:
> David Woolley wrote:
>
>> In article <[EMAIL PROTECTED]>,
>> Aggie <[EMAIL PROTECTED]> wrote:
>>
>>> But the weird thing is: NTPD will adjust the time on the client half
>>> way between the server and 1970 Jan 1. For example, if the clock on my
>>
>> PS. Unless
10 matches
Mail list logo