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
Aggie wrote:
> 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,
> th
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 Utterback wrote:
> 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 ntpd
szor,
I routinely build on a sparc-sun-solaris2.9 machine with gcc 3.4.3 and do
not see the problem you describe.
I'm also not sure what question to ask yet to help find the solution.
H
___
questions mailing list
questions@lists.ntp.org
https://lists.
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(
