oading network or servers. Once per 10 seconds is way
too frequent.
--
Miroslav Lichvar
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Tue, Sep 02, 2014 at 02:32:37PM +0200, Kay Sievers wrote:
> On Tue, Sep 2, 2014 at 1:15 PM, Miroslav Lichvar wrote:
> >> There is also some code in src/timesync/timesyncd-manager.c +209:
> >> /* re-arm timer with increasing timeout,
> >> in case
On Fri, Aug 29, 2014 at 06:38:49PM +0200, Kay Sievers wrote:
> On Wed, Aug 27, 2014 at 4:47 PM, Miroslav Lichvar wrote:
> > ---
> > src/timesync/timesyncd-manager.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
>
> It did not apply without the earlier
On Fri, Aug 29, 2014 at 06:31:10PM +0200, Kay Sievers wrote:
> On Wed, Aug 27, 2014 at 4:47 PM, Miroslav Lichvar wrote:
> > After receiving a reply from the server, allow two missed replies before
> > switching to another server to avoid unnecessary clock hopping when
> > pac
On Fri, Aug 29, 2014 at 06:45:24PM +0200, Kay Sievers wrote:
> On Wed, Aug 27, 2014 at 4:47 PM, Miroslav Lichvar wrote:
> > When all servers are exhausted, wait for one poll interval before trying
> > to connect again to the first server in the list. Also, keep increasing
> >
On Fri, Aug 29, 2014 at 06:29:54PM +0200, Kay Sievers wrote:
> On Wed, Aug 27, 2014 at 4:47 PM, Miroslav Lichvar wrote:
> > The shortest time constant that is stable with the kernel PLL (compiled
> > with SHIFT_PLL=2) is about log2 of update interval - 3. Set the constant
> >
The kernel timestamp (recv_time) is made earlier than current time
(now_ts), use the timestamp captured before sending packet directly.
---
src/timesync/timesyncd-manager.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesy
---
src/timesync/timesyncd-manager.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesyncd-manager.c
index 3339606..2b0580c 100644
--- a/src/timesync/timesyncd-manager.c
+++ b/src/timesync/timesyncd-manager.c
@@
problem in the function adjusting the polling
interval, it doesn't consider jitter. When the jitter is large it
goes for a shorter interval instead of longer, making everything
worse. My suggestion would be to include the approach used in ntpd
(search for CLOCK_PGATE in the sources).
Miro
When all servers are exhausted, wait for one poll interval before trying
to connect again to the first server in the list. Also, keep increasing
the polling interval to make sure a client not getting any valid replies
will not send requests to any server more frequently than is allowed by
the maxim
NTPv4 servers don't reply with unsynchronized status when they lost
synchronization, they only keep increasing the root dispersion and it's
up to the client to decide at which point they no longer consider it
synchronized.
Ignore replies with root distance over 5 seconds.
---
src/timesync/timesyn
The shortest time constant that is stable with the kernel PLL (compiled
with SHIFT_PLL=2) is about log2 of update interval - 3. Set the constant
to poll - 2 to make room for one missed update.
---
src/timesync/timesyncd-manager.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
After receiving a reply from the server, allow two missed replies before
switching to another server to avoid unnecessary clock hopping when
packets are getting lost in the network.
---
src/timesync/timesyncd-manager.c | 27 ++-
src/timesync/timesyncd-manager.h | 1 +
2 fi
---
src/timesync/timesyncd-manager.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesyncd-manager.c
index d80c72f..60f39c6 100644
--- a/src/timesync/timesyncd-manager.c
+++ b/src/timesync/timesyncd-manager.c
@@ -574,7 +574,
---
src/timesync/timesyncd-manager.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesyncd-manager.c
index 9f12149..d1f77a8 100644
--- a/src/timesync/timesyncd-manager.c
+++ b/src/timesync/timesyncd-manager.c
@@ -735,7 +735,
ould never delay the boot by default for
> external conditions, such as network connectivity. hence, by default
> waiting for a network interface before we finish boot, and even waiting
> for a way to connect to an NTP server is not OK.
What services with dependency on the target do we use by
rift through when network is congested,
ability to deal with broken clocks (as in some virtual machines) and
monotonic time just for a super fast update seems like a bad choice to
me.
I'm sure timesyncd will be significantly improved over time, but
currently I'd not describe it as "mor
nd actual
> consumer products.
Ok, how exactly are you feeding the NTP client? Perhaps it's something
we could use in chronyd too.
--
Miroslav Lichvar
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Tue, Aug 26, 2014 at 02:21:10PM +0200, Lennart Poettering wrote:
> On Tue, 26.08.14 11:41, Miroslav Lichvar (mlich...@redhat.com) wrote:
> > To have timedated/timedatectl managing the right NTP service on
> > distributions like Fedora.
>
> I don't really think that
On Tue, Aug 26, 2014 at 03:27:10AM +0200, Lennart Poettering wrote:
> On Thu, 21.08.14 12:49, Miroslav Lichvar (mlich...@redhat.com) wrote:
>
> > This is useful for installations where some other service than
> > systemd-timesyncd is used to synchronize the system clock.
>
&
lect it for
timedated. In 216 the ntp-units.d directory is ignored and timedated
always controls timesyncd. I think it would be nice if this was
configurable at least at compile time and I sent a patch for that
yesterday.
--
Miroslav Lichvar
___
systemd-deve
This is useful for installations where some other service than
systemd-timesyncd is used to synchronize the system clock.
---
configure.ac | 9 +
src/timedate/timedated.c | 10 +-
2 files changed, 14 insertions(+), 5 deletions(-)
diff --git a/configure.ac b/configure.
22 matches
Mail list logo
