Description of problem: When synchronized via ntp (chronyd), MCC doesn't allow the administrator to configure a local ntp server (IP address or local domain name) Reproducible: Steps to Reproduce:
CC: (none) => mageia, thierry.vignaud
CC: (none) => anaselli
IIRC drakxclock tool sets a pool of server (0..2 as prefix) from a given one, so if we add an option to set a custom server what should we trust? I mean a user could add a single server just for the local network or a pool. If we decide for him we could be wrong just because guessing. Which is the right approach for a customization of this kind?
On most company networks (middle size & big size), the NTP protocol is reject by the firewalls. All the systems must be synchronized on the NTP servers owned by the company. Ex: radio synchronized (like DCF77 in europe) or atomic synchronized on ministry networks (http://www.atomic-clock.galleon.eu.com/time-servers/time-servers.html) On mageia, we can do that only by hand by editing the "chrony.conf" file. Why can't we do that with drake xclock ? Just add a custom entry for an IP address or a FQDN
I didn't say you are not right :p I just said which is the right way to configure it, because an old design must be changed for that. So we could leave all as it is and provide an input dialog in which you can insert one server and we configure a pool like 0.yourserver 1.yourserver 2.yourserver as we do now, or provide an improved input dialog in which you can add a single or a list of server. This last would change the way in which we get and set the servers into the configuration file, that is not only for chronyd, but also for ntpd. And if you use manaclock even for systemd-timesyncd
Ok, excuse-me to respond so late. Il think the admin can have two choices (check box) : - "Internet NTP" with the "old" design - "local ntp" : the Internet ntp list is disabled and an input box allows the admin to enter the IP address or domain name of its choice.
no worries :) I'm implementing such a feature in manaclock. Unfortunately i had some problems that didn't allow me to finish the implementation. So at least a tool in mageia will support that soon.
Severity: minor => enhancement
Summary: Can't configure a locale ntp server with MCC (drakclock) => Feature: configure a locale ntp server with MCC (drakclock)
Summary: Feature: configure a locale ntp server with MCC (drakclock) => Feature: configure a local ntp server with MCC (drakclock)
commit 72e8ffa7bc218e163d889812d7f00f738b7aefd2 Author: Angelo Naselli <anaselli@...> Date: Tue Feb 2 23:22:34 2016 +0100 manaclock - Added local NTP server setup mga#17569 --- Commit Link: http://gitweb.mageia.org/software/manatools/commit/?id=72e8ffa7bc218e163d889812d7f00f738b7aefd2
(In reply to Mageia Robot from comment #6) > commit 72e8ffa7bc218e163d889812d7f00f738b7aefd2 > Author: Angelo Naselli <anaselli@...> > Date: Tue Feb 2 23:22:34 2016 +0100 > > manaclock - Added local NTP server setup mga#17569 > --- > Commit Link: > > http://gitweb.mageia.org/software/manatools/commit/ > ?id=72e8ffa7bc218e163d889812d7f00f738b7aefd2 The implementation of this feature in manaclock worked fine when I tried it. Dunno whether it'd be easy to do the same for DrakX
CC: (none) => marja11Version: 5 => CauldronAssignee: bugsquad => thierry.vignaud