| Summary: | Mageia 7 Final: Add NTP servers from NTP.br, installed and enabled by default? | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | drivalinux <drivalinux> |
| Component: | New RPM package request | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | guillomovitch, isobuild, lists.jjorge, luigiwalser, mageiatools, marja11, nicolas.salguero |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
drivalinux
2019-06-25 21:07:52 CEST
NTP.br: pool.ntp.br - More used. NTP Pool Project: https://www.pool.ntp.org/zone/br - Less used. I don't know where we get our list of ntp servers from, from the ntp package or not. CC'ing some people who know more about this than me. CC:
(none) =>
guillomovitch, isobuild, lists.jjorge, luigiwalser, mageiatools, marja11, nicolas.salguero @ drivalinux What is wrong with the br.pool.ntp.org ntp servers, that we _do_ have? (In reply to drivalinux from comment #0) > Why Mageia Linux 7 RC 1 (updated 25 June 2019), does not have NTP servers > from NTP.br? While this is an interesting project, we use the worldwide servers of the NTP pool project project, which allows automatic finding of a nearby server using the pool.ntp.org DNS name. You can see there are 33 servers in Brazil : https://www.ntppool.org/zone/br I feel the ntp.br project should work with the world wide project, so that it's servers are used by any ntp software. You can contact them here : https://manage.ntppool.org/manage So this bug is invalid Resolution:
(none) =>
INVALID I understand. NTP.br: The official NTP of Brazil. Thank you! Center of Study and Research in Network Technology and Operations - CEPTRO: http://www.ceptro.br/CEPTRO/EnglishHome http://www.ntp.br - NTP.br (Brazilian Legal Time over Internet), provided by the National Observatory. Thank you! I'm using Mageia Linux 7 Final (released 23 June 2019 / updated 30 June 2019), and the system complies with this bug. Thank you! |