Rob schrieb:
Martin Burnicki martin.burni...@meinberg.de 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
Jochen Bern wrote:
On 17.04.2014 14:00, questions-requ...@lists.ntp.org digested:
From: Martin Burnicki martin.burni...@meinberg.de
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
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
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
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
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
(Sorry, MIME setting didn't have an effect yet.)
On 22.04.2014 13:07, questions-requ...@lists.ntp.org digested:
From: Mimiko vbv...@gmail.com
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
Martin Burnicki martin.burni...@meinberg.de wrote:
Rob schrieb:
Martin Burnicki martin.burni...@meinberg.de 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
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 17.04.2014 14:00, questions-requ...@lists.ntp.org digested:
From: Martin Burnicki martin.burni...@meinberg.de
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*
On 2014-04-17, Jochen Bern jochen.b...@linworks.de wrote:
On 17.04.2014 14:00, questions-requ...@lists.ntp.org digested:
From: Martin Burnicki martin.burni...@meinberg.de
Usually it is sufficient to set the RTC on system shutdown, so that it
keeps time while the machine is powered off
Mimiko wrote:
I don't understand, why so much trouble about clocks in linux?
You're wrong. Most trouble with clocks is due to Windows.
In
windows systems, there is a default time service which synchronise with
some time server or domain controller and automatically sets hw (and
maybe
Martin Burnicki martin.burni...@meinberg.de 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
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 the RTC chip.
[]
On 2014-04-16, David Taylor david-tay...@blueyonder.co.uk.invalid 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
On 14/04/2014 22:28, William Unruh wrote:
[]
Under any unix derivative the system time is UTC (or for some TAI)
Under Windows it can be local or UTC.
ntp internally always uses UTC as you say.
Windows internally always uses UTC, if that's what you mean by system
time.
It's the RTC (or BIOS
On 2014-04-15, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 14/04/2014 22:28, William Unruh wrote:
[]
Under any unix derivative the system time is UTC (or for some TAI)
Under Windows it can be local or UTC.
ntp internally always uses UTC as you say.
Windows internally
On 15/04/2014 07:24, William Unruh wrote:
[]
No, I meant that Windows at least did (pre Win7?) use local time as
system time.
And I seem to recall that even now it can use localtime as systemtime.
But I do not run Windows so cannot test anything.
Win-32 (i.e. Windows NT and later) uses UTC as
Phil W Lee p...@lee-family.me.uk wrote:
David Taylor david-tay...@blueyonder.co.uk.invalid considered Tue,
15 Apr 2014 07:32:48 +0100 the perfect time to write:
On 15/04/2014 07:24, William Unruh wrote:
[]
No, I meant that Windows at least did (pre Win7?) use local time as
system time.
And I
On 14.04.2014 11:47, Harlan Stenn wrote:
So in general, ntpd is running on the box?
Yes, its running as a service. Its acting as a time server very well for
a year.
What does ntpd talk to during the months it takes for the time to drift
away by 30-60 seconds?
No logs about this drift of
On 13/04/14 08:40, Mimiko wrote:
Hello.
I'm running a ntpd service on a local server for time synchronization of
all servers and workstations. Ntpd works fine, synchronizing linux and
windows. The problem is that hw clock of the time server is not
synchronized periodically and it is not in
Mimiko writes:
On 14.04.2014 11:47, Harlan Stenn wrote:
So in general, ntpd is running on the box?
Yes, its running as a service. Its acting as a time server very well for
a year.
What does ntpd talk to during the months it takes for the time to drift
away by 30-60 seconds?
No
On 14.04.2014 13:01, Harlan Stenn wrote:
I would expect ntpd -q to correct the system clock, not the BIOS clock.
So ntpd has nothing to do with hardware clock.
This is the command line which starts ntpd as service:
/srv/ntpd/bin/ntpd -p /var/run/ntpd.pid -g -l /srv/ntpd/log/ntpd.log -s
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 hwtime to correct RTC
On 2014-04-13, Mimiko vbv...@gmail.com wrote:
Hello.
I'm running a ntpd service on a local server for time synchronization of
all servers and workstations. Ntpd works fine, synchronizing linux and
windows. The problem is that hw clock of the time server is not
synchronized periodically
Mimiko writes:
On 14.04.2014 13:01, Harlan Stenn wrote:
I would expect ntpd -q to correct the system clock, not the BIOS clock.
So ntpd has nothing to do with hardware clock.
This is the command line which starts ntpd as service:
/srv/ntpd/bin/ntpd -p /var/run/ntpd.pid -g -l
On 2014-04-14, Harlan Stenn st...@ntp.org wrote:
Mimiko writes:
On 14.04.2014 13:01, Harlan Stenn wrote:
I would expect ntpd -q to correct the system clock, not the BIOS clock.
So ntpd has nothing to do with hardware clock.
This is the command line which starts ntpd as service:
William Unruh writes:
On 2014-04-14, Harlan Stenn st...@ntp.org wrote:
...
NTP uses UTC, not localtime. So at startup, if the OS sets the clock
using the BIOS clock it will use localtime instead of UTC, and in 23
out of 24 areas of the world, that will be different from UTC.
That depends
On 14.04.2014 22:45, Harlan Stenn wrote:
I would like to see the log files for that situation. I suspect a
different problem. When -g is given we allow the maximum possible time
adjustment for the initial time correction. Only after that has been
done do we re-enable the panic limit that
Hello.
I'm running a ntpd service on a local server for time synchronization of
all servers and workstations. Ntpd works fine, synchronizing linux and
windows. The problem is that hw clock of the time server is not
synchronized periodically and it is not in sync. So in case of server
Mimiko writes:
I'm running a ntpd service on a local server for time synchronization of
all servers and workstations. Ntpd works fine, synchronizing linux and
windows. The problem is that hw clock of the time server is not
synchronized periodically and it is not in sync. So in case of
31 matches
Mail list logo
