On Tue, 22 Apr 2014 10:42:58 GMT, Jochen Bern
wrote:
>On 22.04.2014 11:45, questions-requ...@lists.ntp.org digested:
>> From: Caecilius
>>
>> 1. tcpdump shows that the packet-level behaviour is the same for ntp
>> 4.2.4p4 and 4.2.6p2. Namely packets to a given peer switch from one
>> source IP
Martin Burnicki wrote:
> Rob schrieb:
>> Martin Burnicki wrote:
>>> Imagine what happens if you shut down Windows *before* DST starts and
>>> reboot *after* DST has started? Your system time will be off by 1 hour
>>> because standard time has been written to the RTC at shutdown, but DST
>>> is as
(Sorry, "MIME" setting didn't have an effect yet.)
On 22.04.2014 13:07, questions-requ...@lists.ntp.org digested:
> From: Mimiko
>
> Asking about some much trouble in time keeping in linux, I meant about
> not having a out of the box time synchronization with some server on
> internet, like wi
Hello.
I didn't reply on messages a long time. This thread became quite
interesting. Indeed it is a very complicated thing in to agree on which
time to run the system and RTC. Mostly because of windows, which follows
there own standards.
Meanwhile I did some tests on a windows xp system conf
On 21.04.2014 02:15, questions-requ...@lists.ntp.org digested:
> From: David Woolley
>
> Such digesters normally offer a MIME digest mode. Thunderbird can cope
> with that and allows you to extract an individual message from that and
> thread a reply to it properly.
Found and flipped (as I d
On 22.04.2014 11:45, questions-requ...@lists.ntp.org digested:
> From: Caecilius
>
> 1. tcpdump shows that the packet-level behaviour is the same for ntp
> 4.2.4p4 and 4.2.6p2. Namely packets to a given peer switch from one
> source IP to the other approximately every 10 minutes.
>
> So the pack
On 22/04/2014 10:44, Martin Burnicki wrote:
David Taylor wrote:
On 16/04/2014 14:50, Martin Burnicki wrote:
[]
However, when the NTP service is shut down then it stops disciplining
the system time anyway and thus calls the Windows API which sets the
time with the current time as new time. This
David Taylor wrote:
On 16/04/2014 14:50, Martin Burnicki wrote:
[]
However, when the NTP service is shut down then it stops disciplining
the system time anyway and thus calls the Windows API which sets the
time with the current time as new time. This should force Windows to
update the time in th
David Taylor schrieb:
On 14/04/2014 10:33, David Woolley wrote:
[]
This is something that is done by the operating system (e.g. every 11
minutes in Linux, or by cron jobs in some other systems), not by ntpd.
Some people object to this behaviour in Linux because it prevents the
effective use of h
Jochen Bern wrote:
On 17.04.2014 14:00, questions-requ...@lists.ntp.org digested:
From: Martin Burnicki
Usually it is sufficient to set the RTC on system shutdown, so that it
keeps time while the machine is powered off
That is, of course, assuming that the machine in question *has* an
*order
Brian Inglis wrote:
On 2014-04-19 16:16, Casper H.S. Dik wrote:
Jos van de Ven writes:
The registry key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
And then add a DWORD (32bit) value and name it RealTimeIsUniversal
with a
value of 1
It should be working with wi
Rob schrieb:
Martin Burnicki wrote:
Imagine what happens if you shut down Windows *before* DST starts and
reboot *after* DST has started? Your system time will be off by 1 hour
because standard time has been written to the RTC at shutdown, but DST
is assumed to be read from the RTC at boot time
12 matches
Mail list logo
