Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #880108
| From | Vincent Blut <vincent.debian@free.fr> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#889010: should it rather be network online target in the service file? |
| Date | 2018-02-06 17:00 +0100 |
| Message-ID | <vgdP4-pP-29@gated-at.bofh.it> (permalink) |
| References | <veiJc-4FN-7@gated-at.bofh.it> <veiJc-4FN-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Control: tags -1 moreinfo
Hi Christian,
On Thu, Feb 01, 2018 at 09:43:07AM +0100, Christian Ehrhardt wrote:
>Package: chrony
>Version: 3.2-2
>
>Description:
>Conversions of old $network behavior should be on online target [2].
>And I think for chrony it makes sense to start when it really is
>online to not rely too much on the hooks to set it online.
Prior to the 3.0-1 release, we used to heavily rely on the hooks as the
time sources weren’t polled by chronyd due to the use of the “offline”
option. This behaviour wasn’t satisfactory to me, so I decided it was
time to change it for Debian Stretch so what's happening now is:
- If the network is up:
- chronyd starts
- chronyc online runs, but doesn't actually do anything
- names are resolved
- sources are added as online
- burst is executed
- If the network is down:
- chronyd starts
- chronyc online doesn't run
- chronyd is periodically trying, in exponentially increasing
interval, to resolve the pool.ntp.org name, but fails
- network is up
- chronyc online runs from the hooks
- chronyd resolves the name
- sources are added as online
- burst is executed
Also, I think chronyd should be started quite early so the clock
frequency offset is set from the drift file. It should also be noted
that when used with a reference clock, chronyd does not necessarily need
network nor DNS.
However, if starting chronyd after the network is fully up is something
you really are looking for, I think you should start it after
nss-lookup.target‽
>Ubuntu-Bug:
>https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746458
>Fix-in-Review:
>https://git.launchpad.net/~paelzer/ubuntu/+source/chrony/commit/?id=2baea8e0bde5d6a1de60098019fb658a4a94d489
>
>[1]: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844
>[2]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
>
>--
>Christian Ehrhardt
>Software Engineer, Ubuntu Server
>Canonical Ltd
Cheers,
Vincent
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#889010: should it rather be network online target in the service file? Christian Ehrhardt <christian.ehrhardt@canonical.com> - 2018-02-01 09:50 +0100
Bug#889010: should it rather be network online target in the service file? Vincent Blut <vincent.debian@free.fr> - 2018-02-06 17:00 +0100
Bug#889010: should it rather be network online target in the service file? Christian Ehrhardt <christian.ehrhardt@canonical.com> - 2018-02-08 08:20 +0100
csiph-web