Caecilius nospam@spamless.invalid wrote:
I guess that something has been added between 4.2.4p4 and 4.2.6p2
that's making ntp take notice of the two different routes. But I don't
understand why it should care: that's the network layer's problem, and
there will often be multiple routes between
David Taylor david-tay...@blueyonder.co.uk.invalid writes:
It would be helpful if the operating systems were to agree on how to use
the BIOS clock. Not every computer travels during the year, and not
every location has summer-time transitions.
Right; dual boot (or more) is a problem and with
On 20.04.2014 14:00, questions-requ...@lists.ntp.org digested:
From: David Taylor david-tay...@blueyonder.co.uk.invalid
It would be helpful if the operating systems were to agree on how to use
the BIOS clock.
Well, if I understand the statements about Win correctly, they *do* now,
at least
On 2014-04-20, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 19/04/2014 18:27, William Unruh wrote:
[]
Why in the world would that be helpful? Wall clock time changes when you
move or travel. Wall clock changes twice a year at DST transitions. It
is a silly thing to have
On 20/04/2014 18:44, William Unruh wrote:
[]
Users never see the output of the RTC.
So you've never needed to alter a parameter in the BIOS - lucky you!
--
Cheers,
David
Web: http://www.satsignal.eu
___
questions mailing list
On 19.04.2014 14:00, questions-requ...@lists.ntp.org digested:
From: David Woolley david@ex.djwhome.demon.invalid
On 18/04/14 21:15, Jochen Bern wrote:
[Unthreaded reply.]
Are you aware that you mail/news client is broken and is not threading
your replies properly. If you are using
On 2014-04-20, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 20/04/2014 18:44, William Unruh wrote:
[]
Users never see the output of the RTC.
So you've never needed to alter a parameter in the BIOS - lucky you!
Users never see the output of the RTC. If you are altering
On 20.04.2014 22:35, Jochen Bern wrote:
I haven't searched for an *add-on* to shoehorn into my
Thunderbird that might further grok digest mails, though.
(FWIW, I found Undigestify 0.8
https://addons.mozilla.org/en-US/thunderbird/addon/undigestify/
which would probably allow for correct
On 20/04/14 21:35, Jochen Bern wrote:
Anyway, if failure to produce normal threading headers is as verboten
as you claim, then it's not my user agent that is broken but the fact
that the mailinglist server offers digest-mode subscriptions in the
first place. (And, by the way, prefixes them
On Fri, Apr 18, 2014 at 9:43 PM, Jason Rabel
ja...@extremeoverclocking.comwrote:
Greg,
As others have suggested, any client running NTP should point to *at
least* 3 time sources (usually ~5 is preferred)... The reason
being if one server goes wacko, but the other two agree, then the client
On 2014-04-21, GregL greg.leibfr...@gmail.com wrote:
I really do appreciate all the responses to my questions. I would like to
give this the proper respect it deserves and evaluate some best practices
with respect to time synchronization across our enterprise systems. I
would rather make
On 2014-04-20, Jochen Bern jochen.b...@linworks.de wrote:
You might want to note from the very first line in my replies that I'm
subscribed to the mailing list in digest mode, and chances are that a
quick inspection of the headers on your end would have shown you not
only In-Reply-To: and
12 matches
Mail list logo
