D.Venu Gopal wrote:
David Woolley wrote:
Venu Gopal wrote:
Its clear that CPU is heavily loaded which might be leading to loss of
ticks. Yet to check the DMA status for
CPU loading doesn't cause lost timer interrupts. (More precisely
overruns.)
So its the DISK I/O thats causing loss
So its the DISK I/O thats causing loss of ticks ?
My first Red Hat system defaulted to no-DMA for IDE disks. (Yes,
that was a long time ago.) With that setup, it was simple to generate
lots of lost timer interrupts: just keep the disk busy doing reads.
(Seeks don't count. Read consecutive
Evandro,
Evandro Menezes wrote:
But doesn't symmetric association require authorization or is it only
true when there's a keys file?
AFAIK peer associations do require authentication configured correctly.
I ask because after following this thread, I noticed that NTP running
on our NAS had
Hal Murray wrote:
So its the DISK I/O thats causing loss of ticks ?
My first Red Hat system defaulted to no-DMA for IDE disks. (Yes,
that was a long time ago.) With that setup, it was simple to generate
lots of lost timer interrupts: just keep the disk busy doing reads.
(Seeks don't
On Mar 13, 3:56 am, Martin Burnicki [EMAIL PROTECTED]
wrote:
The default was that ntpd just dropped those requests, i.e. didn't send a
response at all, in which case the w32time clients were unable to
synchronize to the NTP server, unless they were reconfigured correctly to
send client
On Mar 12, 11:33 am, Unruh [EMAIL PROTECTED] wrote:
It may not belong on time.microsoft.com but does on microsoft by making it
hard to use any other server.
Using another NTP server isn't hard on Windows, in fact it is dead
simple and easier than configuring the reference ntpd implementation,
On Mar 13, 3:56 am, Martin Burnicki [EMAIL PROTECTED]
wrote:
Do the Windows system run ntpd or w32time? If they run ntpd then
authentication could be configured correctly. I don't know how any version
of w32time could be configured to support NTP's symmetric keys or even
autokey.
They run
Ryan Malayter wrote:
On Mar 13, 3:56 am, Martin Burnicki [EMAIL PROTECTED]
wrote:
The default was that ntpd just dropped those requests, i.e. didn't send a
response at all, in which case the w32time clients were unable to
synchronize to the NTP server, unless they were reconfigured correctly
Evandro,
Remember, enable/disable auth has nothing to do with authentication
itself, just whether new associations can be mobilized if no
authentication is used. In your case a symmetric passive association was
apparently mobilized and began sending mode-2 packets just as if a
legitimate peer
Maarten Wiltink wrote:
As a software guy, I've wondered before about the monolithic nature of
the NTP package. Splitting it into a client and server part might make
some people (think OpenBSD) very happy. The objection when raised earlier
was that the server may be asked for statistics about
Johnson, John-P63914 wrote:
One instance of ntpd is all that is necessary to perform both of these
tasks at the same time.
I realize that what I am trying to do is very easily accomplished with
one
instance of ntpd. However, I assure you that the manner in which I am
trying to
11 matches
Mail list logo