** Changed in: chrony (Debian)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746458
Title:
should it rather be network online target in the service file?
After a discussion with the Debian maintainer I agree to revert this change.
I uploaded chrony_3.2-2ubuntu3_source.changes [1] with that change.
[1]: https://launchpad.net/ubuntu/+source/chrony/3.2-2ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Changed in: chrony (Debian)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746458
Title:
should it rather be network online target in the service file?
To manage
This bug was fixed in the package chrony - 3.2-2ubuntu2
---
chrony (3.2-2ubuntu2) bionic; urgency=medium
* d/control: use to nss instead of tomcrypt (in main) (LP: #1744072)
* d/chrony.conf: use ubuntu ntp pool and server (LP: #1744664)
* d/chrony.default, d/chrony.service: supp
** Changed in: chrony (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746458
Title:
should it rather be network online target in the service file?
To manage no
Note: in the sense of the link above chrony is not a classic server but
a "client software that cannot operate without network" as it need to
sync time from/to somewhere.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746458
Title:
should it rather be net
Yes according to [1] the most direct translation to the old LSB $network would
be:
Wants=network-online.target
After=network-online.target
And that is what chrony was and IMHO should be again.
That also would fix some rare cases where network comes up late and chrony
starts in offline mode.
Rely
