On Tue, Aug 26, 2014 at 09:08:47AM -0700, Marcel Holtmann wrote:
ConnMan is a single daemon solution doing NTP, DHCP and DNS all in
one place. Any sort of callouts are costing time. And that is time
that has a visible user impact. There is nothing that justifies to
have a bit more nanosecond
Hi Miroslav,
ConnMan is a single daemon solution doing NTP, DHCP and DNS all in
one place. Any sort of callouts are costing time. And that is time
that has a visible user impact. There is nothing that justifies to
have a bit more nanosecond accuracy of synchronized time than making
the user
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.
What's the rationale here?
On Tue, 26.08.14 11:41, 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.
What's the rationale here?
To have timedated/timedatectl managing the right NTP service on
On Tue, Aug 26, 2014 at 4:21 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 26.08.14 11:41, 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.
What's the
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 timedated should manage an NTP
2014-08-26 14:37 GMT+02:00 Lennart Poettering lenn...@poettering.net:
On Tue, 26.08.14 16:34, Andrei Borzenkov (arvidj...@gmail.com) wrote:
I don't really think that timedated should manage an NTP server like
ntpd/chrony. timedated's primary job is to be a service to GNOME and
other DEs.
Hi Miroslav,
To have timedated/timedatectl managing the right NTP service on
distributions like Fedora.
I don't really think that timedated should manage an NTP server like
ntpd/chrony.
I'm talking about NTP clients, not servers. Writing a good NTP client
is the difficult part, making
On Tue, Aug 26, 2014 at 07:50:23AM -0700, Marcel Holtmann wrote:
and writing a good DHCP client was supposedly also really hard.
Guess what we have done that twice now and both of our clients are
better than everything else out there. And guess what, we did the
same for NTP.
Are you saying
Hi Miroslav,
and writing a good DHCP client was supposedly also really hard.
Guess what we have done that twice now and both of our clients are
better than everything else out there. And guess what, we did the
same for NTP.
Are you saying timesyncd is already better than chronyd or ntpd?
On Tue, 26.08.14 15:44, Miroslav Lichvar (mlich...@redhat.com) wrote:
timedated's primary job is to be a service to GNOME and
other DEs. But if an admin wants to upgrade to a full NTP server, then
he should really enable/disable that with systemctl or a similar
command.
Distributions
On Tue, 26.08.14 15:56, Simon Peeters (peeters.si...@gmail.com) wrote:
2014-08-26 14:37 GMT+02:00 Lennart Poettering lenn...@poettering.net:
On Tue, 26.08.14 16:34, Andrei Borzenkov (arvidj...@gmail.com) wrote:
I don't really think that timedated should manage an NTP server like
On Aug 26, Lennart Poettering lenn...@poettering.net wrote:
If it makes you happy, then I can add a big warning to configure, if
people build things and don't specify their own NTP servers...
The history is full of people who got burned by using somebody's else
NTP servers without permission,
В Tue, 26 Aug 2014 19:19:01 +0200
Lennart Poettering lenn...@poettering.net пишет:
On Tue, 26.08.14 17:45, Miroslav Lichvar (mlich...@redhat.com) wrote:
On Tue, Aug 26, 2014 at 07:50:23AM -0700, Marcel Holtmann wrote:
and writing a good DHCP client was supposedly also really hard.
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.
What's the rationale here?
We recently removed support for configuring arbitrary NTP servers from
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
16 matches
Mail list logo
