Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42636 - [systemd] Option ntp-server(42) Ignored in DHCP Response
Attached to Project:
Arch Linux
Opened by Martin Gallant (martyg) - Friday, 31 October 2014, 16:26 GMT
Last edited by Dave Reisner (falconindy) - Friday, 31 October 2014, 16:54 GMT
Opened by Martin Gallant (martyg) - Friday, 31 October 2014, 16:26 GMT
Last edited by Dave Reisner (falconindy) - Friday, 31 October 2014, 16:54 GMT
|
DetailsDescription:
systemd fails to set up timesyncd.service with the NTP server provided by DHCP as documented in the Wiki, Ref. https://wiki.archlinux.org/index.php/Systemd-timesyncd I just tested this on systemd version 216-3 on x86_64 Installing NetworkManager does not fix this - should a separate bug be filed there as well? Steps to reproduce: Pristine base install, rebooted # Use ip link to retrieve interface name dhcpcd -T enps0s25 # Observe ntp_servers stanza in response systemctl start dhcpcd@enps0s25 timedatectl set-ntp true # Start NTP client timedatectl # Confirm NTP is enabled and in sync journalctl -f # Observe NTP on default time*.google.com |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 31 October 2014, 16:54 GMT
Reason for closing: Upstream
Additional comments about closing: Nothing here for Arch to do/fix.
Friday, 31 October 2014, 16:54 GMT
Reason for closing: Upstream
Additional comments about closing: Nothing here for Arch to do/fix.
Comment by Martin Gallant (martyg) -
Friday, 31 October 2014, 16:40 GMT
Also reproduced on systemd 217.3 (Testing)
Comment by Dave Reisner (falconindy) -
Friday, 31 October 2014, 16:53 GMT
Nothing to do in Arch -- please report this upstream. Either it's a bug, or the DHCP client (yet?) doesn't honor NTP options in the response.