On Thu, Nov 27, 2014 at 01:19:48PM -0500, Miloslav Trmač wrote:
- Original Message -
One suggestion was to install it as a dependency of the NTP packages.
Is this a good idea? Should this first go through the Fedora change
process or at least be documented somewhere?
I think
On Mon, 01.12.14 15:55, Miroslav Lichvar (mlich...@redhat.com) wrote:
Beside the selection of the NTP service that should enabled/disabled,
there are some minor differences in the functionality. For instance,
when setting the time, timedatex compensates for the time spent in the
polkit
On Tue, 2014-11-25 at 18:26 +0100, Lennart Poettering wrote:
On Tue, 25.11.14 11:08, Michael Catanzaro (mcatanz...@gnome.org) wrote:
On Tue, 2014-11-25 at 17:15 +0100, Lennart Poettering wrote:
I am sorry, but timedated is really not the place to control NTP
*server* software. It's
- Original Message -
If we want to have this working correctly with chronyd/ntpd, at this point
it seems the only reasonable option is to replace systemd-timedated.
timedatex is a new implementation of the timedate interface that was
recently added to Fedora. It reads the list of NTP
On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote:
Once upon a time, Tomasz Torcz to...@pipebreaker.pl said:
On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote:
Once upon a time, Florian Weimer fwei...@redhat.com said:
Do we even use the DHCP NTP server
On Thu, Nov 27, 2014 at 12:51 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote:
Once upon a time, Tomasz Torcz to...@pipebreaker.pl said:
On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote:
Once upon a time, Florian Weimer
Hi Andrew,
On Thu, Nov 27, 2014 at 10:00 PM, Andrew Lutomirski l...@mit.edu wrote:
On Thu, Nov 27, 2014 at 12:51 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote:
Once upon a time, Tomasz Torcz to...@pipebreaker.pl said:
On Wed, Nov
On Thu, Nov 27, 2014 at 10:53:45PM +0100, Tom Gundersen wrote:
On Thu, Nov 27, 2014 at 10:00 PM, Andrew Lutomirski l...@mit.edu wrote:
On Thu, Nov 27, 2014 at 12:51 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote:
Once upon a time,
On Thu, Nov 27, 2014 at 1:53 PM, Tom Gundersen t...@jklm.no wrote:
Hi Andrew,
On Thu, Nov 27, 2014 at 10:00 PM, Andrew Lutomirski l...@mit.edu wrote:
On Thu, Nov 27, 2014 at 12:51 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote:
Once
On Tue, Nov 25, 2014 at 02:35:12PM -0700, Chris Murphy wrote:
On Tue, Nov 25, 2014 at 10:51 AM, Florian Weimer fwei...@redhat.com wrote:
Some networks have bad NTP service in the sense that they hand out incorrect
time (not just off by a few seconds, but days or months, enough to skew
On 11/26/2014 10:09 AM, Miroslav Lichvar wrote:
We still do. Unless the number of bad servers added from DHCP is large
enough to disrupt the NTP source selection algorithm or the pool
servers are not reachable (NTP traffic blocked), it shouldn't be a big
problem. Of course, without
Once upon a time, Florian Weimer fwei...@redhat.com said:
Do we even use the DHCP NTP server assignment?
I believe it is used for chrony and ntpd, don't know about sysmted's new
implementation.
--
Chris Adams li...@cmadams.net
--
devel mailing list
devel@lists.fedoraproject.org
On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote:
Once upon a time, Florian Weimer fwei...@redhat.com said:
Do we even use the DHCP NTP server assignment?
I believe it is used for chrony and ntpd, don't know about sysmted's new
implementation.
systemd-timesyncd uses
Once upon a time, Tomasz Torcz to...@pipebreaker.pl said:
On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote:
Once upon a time, Florian Weimer fwei...@redhat.com said:
Do we even use the DHCP NTP server assignment?
I believe it is used for chrony and ntpd, don't know about
This is about bug #1136905 [1], discussed previously on the systemd list
[2] and also on our desktop list [3].
The issue is that systemd-timedated now supports only systemd-timesyncd
for NTP and ignores other NTP services installed on the system. It doesn't
know that chronyd or ntpd is enabled
On Tue, 25.11.14 16:23, Miroslav Lichvar (mlich...@redhat.com) wrote:
This is about bug #1136905 [1], discussed previously on the systemd list
[2] and also on our desktop list [3].
The issue is that systemd-timedated now supports only systemd-timesyncd
for NTP and ignores other NTP services
On 11/25/2014 05:15 PM, Lennart Poettering wrote:
Really? if you want a UI that controls whether NTP server software is
running, why not call into the EnableUnitFiles() APIs directly?
Both chronyd and ntpd are often used as clients. Miroslav wasn't
talking about server usage scenarios, but
On Tue, 2014-11-25 at 17:15 +0100, Lennart Poettering wrote:
I am sorry, but timedated is really not the place to control NTP
*server* software. It's simply, desktopy stuff, for controlling NTP
clients.
Of course, but the desktopy NTP client in Fedora Workstation is chrony,
as you know full
On Tue, 25.11.14 18:04, Florian Weimer (fwei...@redhat.com) wrote:
On 11/25/2014 05:15 PM, Lennart Poettering wrote:
Really? if you want a UI that controls whether NTP server software is
running, why not call into the EnableUnitFiles() APIs directly?
Both chronyd and ntpd are often used as
On Tue, 25.11.14 11:08, Michael Catanzaro (mcatanz...@gnome.org) wrote:
On Tue, 2014-11-25 at 17:15 +0100, Lennart Poettering wrote:
I am sorry, but timedated is really not the place to control NTP
*server* software. It's simply, desktopy stuff, for controlling NTP
clients.
Of course,
On 11/25/2014 06:25 PM, Lennart Poettering wrote:
On Tue, 25.11.14 18:04, Florian Weimer (fwei...@redhat.com) wrote:
On 11/25/2014 05:15 PM, Lennart Poettering wrote:
Really? if you want a UI that controls whether NTP server software is
running, why not call into the EnableUnitFiles() APIs
On Tue, Nov 25, 2014 at 10:51 AM, Florian Weimer fwei...@redhat.com wrote:
Some networks have bad NTP service in the sense that they hand out incorrect
time (not just off by a few seconds, but days or months, enough to skew
certificate validity).
I'm not sure what we're supposed to do about
22 matches
Mail list logo
