Bug 19113 - drakconfig does not configure systemd-timesynd to use NTP servers
Summary: drakconfig does not configure systemd-timesynd to use NTP servers
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: Mageia 6
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords: Junior_job
Depends on:
Blocks:
 
Reported: 2016-08-01 12:03 CEST by Hartmut Goebel
Modified: 2017-01-16 19:34 CET (History)
2 users (show)

See Also:
Source RPM: drakxtools-16.104-1.mga5.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Hartmut Goebel 2016-08-01 12:03:59 CEST 
drakconf (System -> Localization -> Manage data & time) allows setting up the NTP server. But settings here does not effect systemd-timesynd configuration. So systemd-timesynd still uses a compiled-in list of fall-back NTP servers.

drakconf should be changed to write the NTP servers into /etc/systemd/timesyncd.conf, too.

The NTP should be set up in *both* NTP and FallbackNTP variables, since the user would expect only the server he configured to be used - and no others. Espacially since the compiled-in list of fall-back NTP servers are timeX.google.com - which many users doe not want to use for privacy reasons.

Alternatively, if Mageia is operating it's own NTP servers, these could be used as "FallbackNTP".

systemd-timesynd is running by default on any current Mageia 5 system.
Hartmut Goebel 2016-08-01 12:05:50 CEST

Keywords: (none) => Junior_job
Target Milestone: --- => Mageia 6
Source RPM: (none) => drakxtools-16.104-1.mga5.src.rpm
Severity: normal => major

Marja Van Waes 2016-08-01 12:42:05 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=17091

Marja Van Waes 2016-08-01 12:43:03 CEST

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud

Hartmut Goebel 2016-08-01 12:44:51 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=19115

Comment 1 David Walser 2016-08-09 02:57:32 CEST 
The real issue is what you highlighted at the end.  systemd-timesyncd should not be running by default.  It's such a limited NTP implementation that it has no advantage and serves no purpose.  drakclock supports chronyd and ntpd by design; it shouldn't be configuring the useless systemd-timesyncd.  I'm not sure we should have even packaged it.
Samuel Verschelde 2016-10-10 21:35:12 CEST

Version: 5 => Cauldron
Assignee: thierry.vignaud => mageiatools
Whiteboard: (none) => MGA5TOO

Comment 2 David Walser 2017-01-16 19:27:56 CET 
I think the correct resolution for this at this time is WONTFIX, as drakclock shouldn't be bothering to configure systemd-timesyncd, as that's pretty pointless.  Ideally it could disable it if it happens to be enabled.  Thierry did just fix it so that on Mageia 6 it won't be enabled by default anymore, so that's a big step in the right direction.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 3 Angelo Naselli 2017-01-16 19:31:58 CET 
Well FWIW manaclock does it

CC: (none) => anaselli

Comment 4 Angelo Naselli 2017-01-16 19:34:27 CET 
but that i seem to recall that that part works only as root, and i haven't used the FallbackNTP...
Note You need to log in before you can comment on or make changes to this bug.