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
Hello I am trying to sync the date on my older redhat machines and it
seems like daylight savings are not working. I tried replacing the
localtime file with the NewYork file but no changes. This is the
output from ntpdate
stratum 2, precision -19, leap 00, trust 000
refid [18.145.0.30], delay
joe [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hello I am trying to sync the date on my older redhat machines and it
seems like daylight savings are not working. I tried replacing the
localtime file with the NewYork file but no changes. This is the
output from ntpdate
[...]
30
joe wrote:
Hello I am trying to sync the date on my older redhat machines and it
seems like daylight savings are not working. I tried replacing the
localtime file with the NewYork file but no changes. This is the
output from ntpdate
ntpd has NOTHING, repeat NOTHING, to do with daylight
Richard B. Gilbert wrote:
joe wrote:
Hello I am trying to sync the date on my older redhat machines and it
seems like daylight savings are not working. I tried replacing the
localtime file with the NewYork file but no changes. This is the
output from ntpdate
ntpd has NOTHING, repeat
Hello,
I tried to compile the ntp-4.2.4p4 on my sparc-sun-solaris2.9, but I got
error message
What can I do?
I post the end of the make output:
In file included from libopts.c:28:
tokenize.c: In function `copy_cooked':
tokenize.c:51: warning: cast discards qualifiers from pointer target type
Dear all,
I'm very confused on how ntp do the timestamp. I'm running ntpd on
vxworks. It seems to me that the receive timestamp and the Transmit
timestamp are using two different clocks, because when I use ethereal/
wireshark to look up the information of the ntp packet,
the Recevie Time Stamp is:
I'm very confused on how ntp do the timestamp. I'm running ntpd on
vxworks. It seems to me that the receive timestamp and the Transmit
timestamp are using two different clocks, because when I use ethereal/
wireshark to look up the information of the ntp packet,
the Recevie Time Stamp is: Jan 1,
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 update
Are you sure the clock wasn't set in between? Is this a one-time or a
consistent state? What mode packet is this, mode 3 or 4? And why do
you say they are only a few seconds apart? The receive timestamp is the
time the request was received by the server if in a mode 4 packet. In a
mode 3, it
10 matches
Mail list logo
