Last commit made on 2021-05-18
Get this branch:
git clone -b ubuntu/devel https://git.launchpad.net/ubuntu/+source/chrony
Members of Ubuntu Server Dev import team can upload to this branch. Log in for directions.

Branch merges

Branch information


Recent commits

cfee953... by Christian Ehrhardt  on 2021-04-29

changelog: new major release v4.1

Signed-off-by: Christian Ehrhardt <email address hidden>

b53f7c6... by Christian Ehrhardt  on 2021-05-03

d/t/helper-functions: restart explicitly

Several places in the tests behave differently in regard to restart.
- dynamically-add-source directly calls __restart_chronyd and then sleeps
  to have the restart complete.
- __no_system_clock_control restarts implicitly (non obvious from the
  test) and only on some platforms (not on Ubuntu) furthermore it uses
  a different sleep

Clear that by:
- If __no_system_clock_control adds the systemd override only call
  daemon-reload which belongs to the action of updating the config
- have only one place to "sleep after restart" directly in __restart_chronyd
  but still return the retval of the service restart
- have all tests that want/expect to restart (e.g. to read updated
  configuration) explicitly call __restart_chronyd

This improves test readability a lot (especially for people that read
them the first time) and at the same time fixes fails of the test
ntp-server-and-nts-auth on Ubuntu with 4.1~pre1 due to the NTS config
not being picked up.

Submitted to Debian in:

Signed-off-by: Christian Ehrhardt <email address hidden>

5bf95f7... by Christian Ehrhardt  on 2021-02-08


2ed5d29... by Christian Ehrhardt  on 2021-02-08


25089b7... by Christian Ehrhardt  on 2018-03-16

  + debian/docs, debian/README.container: provide documentation about the
    handling of this case.

37ed73d... by Christian Ehrhardt  on 2018-03-15

  + debian/install: make chrony-starter.sh available on install.

898462c... by Christian Ehrhardt  on 2018-03-15

  + debian/chronyd-starter.sh: wrapper to handle special cases in containers
    and if CAP_SYS_TIME is missing. Effectively allows to run NTP server in
    containers on a default installation and avoid failing to sync time (or
    if allowed to sync, avoid multiple containers to fight over it by

44a6bd2... by Christian Ehrhardt  on 2018-03-15

  + debian/chrony.default: new option SYNC_IN_CONTAINER to not fall back
    (Default off)

507d810... by Christian Ehrhardt  on 2018-03-15

  + debian/control: add new dependency libcap2-bin for capsh (usually
    installed anyway, but make them explicit to be sure).

0b36c03... by Christian Ehrhardt  on 2018-03-15

- Set -x as default if unable to set time (e.g. in containers) (LP: 1589780)
  Chrony is a single service which acts as both NTP client (i.e. syncing the
  local clock) and NTP server (i.e. providing NTP services to the network),
  and that is both desired and expected in the vast majority of cases.
  But in containers syncing the local clock is usually impossible, but this
  shall not break the providing of NTP services to the network.
  To some extent this makes chrony's default config more similar to 'ntpd',
  which complained in syslog but still provided NTP server service in those
  + debian/chrony.service: allow the service to run without CAP_SYS_TIME