second reads,
writes and trimming and then it would become quite useful. Especially
since it would free the OS to do anything it wants with the IRQ0 timer
without disrupting wallclock time. "Tickless" kernels have been a thorn
in the side of
nd it (assuming, that is, that
the full argument can be defended...).
Michael Deutschmann
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
out two holes in the argument, with no one posting a defense in
the interim. The first is that polling at 64 isn't enough to stop an
excursion under bad PPS, and the second is that reference clocks aren't
likely to falsetick.
Michael Deutschmann
___
sor, and its omission probably saves only a fraction of a cent per
device. Yet ESR faces a more than $100 markup to have it put back.
---- Michael Deutschmann
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Sat, 3 Mar 2012, Chris Albertson wrote:
> On Fri, Mar 2, 2012 at 4:03 PM, Michael Deutschmann
> > (Not my dream though. If I was to go to the trouble of installing a box
> > outside my home and routing a cable through the wall to my computers,
> > I'd like some weat
ot my dream though. If I was to go to the trouble of installing a box
outside my home and routing a cable through the wall to my computers,
I'd like some weather sensors in the deal as well as just time...)
Michael Deutschmann
___
questions m
fed "Sorry, I'm not sure anymore" rather than lies.
Michael Deutschmann
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
sers
than, say, BT Group...
Michael Deutschmann
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
rference will be trapped inside.
So unless you are trying to get GPS reception indoors, and the noisy
computer is your own, you are in much better shape than the WWV or WWVB
clients. They often have to deal with interference sources that are
between them and the transmitter they want.
Mic
ose are mostly-vertical line of sight transmissions. Unless the
translucent-case computers are sitting in a zeppelin parked between you and
the satellite, they shouldn't hurt very much.
Michael Deutschmann
___
questions mailing list
questions@
ter with support for SS, so even the stratum 1
folks don't have any interest on the EMC side of this issue. (They do
care about other EMI sources that fall in their playground, of course.)
---- Michael Deutschmann
___
questions mailing list
question
pens to be the same frequency as a highly useful public radio clock
signal.
Would the experts here then want the government to mandate spread
spectrum be ON, and if so, what sort of modulation to use?
---- Michael Deutschmann
___
questions mailing list
the cure is simple: When a resolver process is forked, it's
first act should be to reset the stack limit to what it was in the first
place. There's no worry about overcommitting real memory, because
mlockall() is not inherited across forks.
Michael Deutschmann
_
t ntpd before named. So
it should be safe for me to hack the configure script so mlockall() is
used anyway, right?
Also, calling this a "Linux" problem is likely careless. I'd imagine the
root of the incompatibility is probably in the GN
ter 2038-01-19T03:14Z. That should be enough to nail down which NTP era
to use.
(Interesting -- as I write this it is almost exactly 30 years from the
End of Unix Time.)
If you do have 64-bit time_t, why not just read your filesystem's
timestamp on the drift file?
--
15 matches
Mail list logo
