Hal Murray wrote:
I'm pretty sure that some of the systems I've worked on used
the interrupt from the 32 KHz clock chip to drive the scheduler.
From the beginning, IBM PCs did not use the 32kHz clock. It is
possible that some other hardware used a 32kHz derived clock for powered
up
David Woolley wrote:
1.190 MHz (that's what the PC Technical Reference says, but I suspect,
That's actually the AT, not the basic PC. It looks like the AT used a
completely separate clock for for the processor clock, whereas I think
the PC used the 14.1... MHz one as the basic source for
Historically interrupts from the 32kHz clock have not been used, except,
possibly, in powered down states to initiate a restart from suspend or
hibernate. It is possible that has changed very recently, but they
certainly weren't used historically.
Well, at least one of us is confused. Or maybe
On 2008-07-14, Grzegorz Daniluk [EMAIL PROTECTED] wrote:
Steve Kostecke wrote:
What's the real issue here?
[snip]
... the problem is how to remotely audit the ntp server's time without
synchronizing to it.
You can use 'noselect' for this purpose.
And btw. another question, what is the
jlevine [EMAIL PROTECTED] wrote:
I am trying to use a Sunfire X2100 system as a time server using
FreeBSD 6.2. The system clock steps by tens of microseconds every few
minutes with no time software running. I have not seen this on other
non-Sun systems with the identical version of FreeBSD.
Again, read Mark Martinec's web page. He's got a lot of good data.
http://www.ijs.si/time/temp-compensation/
This is almost exactly what I was thinking. Mark's 7 years ahead of me
(laugh)
Thanks for the post, I appreciate the information.
___
Grzegorz,
The selection algorithm has a hard limit of 50 servers all of these can
be considered for selection, but only the best three will survive the
clustering algorithm. The tos maxclock option only effects the number
considered by the pruning algorithm used by the manycast and pool
