group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1746081@xxxxxxxxxxxxxxxxxx>]

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: support /etc/default/chrony
    DAEMON_OPTS in systemd environment (LP: #1746081)
  * d/chrony.service: properly start after networking (LP: #1746458)
  * d/usr.sbin.chronyd: allow to create /run/chrony on demand (LP: #1746444)

 -- Christian Ehrhardt <christian.ehrhardt@xxxxxxxxxxxxx>  Fri, 19 Jan
2018 09:45:38 +0100

** Changed in: chrony (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746081

Title:
  Daemon flags aren't supported ? or unclear how.

Status in chrony package in Ubuntu:
  Fix Released
Status in chrony source package in Xenial:
  Triaged
Status in chrony package in Debian:
  Fix Committed

Bug description:
  Using:

  Ubuntu 16.04.3 LTS
  Chrony package 2.1.1-1

  I wanted to limit a chrony install to be IPV4 only (-4 flag), but from
  the looks of /etc/init.d/chrony and /etc/defaults there doesn't appear
  to be a clean way to do so.

  /etc/init.d/chrony has FLAGS="defaults" set, but the variable never
  appears to be used.  There is also no reference to bring in anything
  from /etc/default/chrony (which doesn't exist either).

  Perhaps I'm overlooking something.  Is there any way to cleanly add a
  startup flag to the service?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746081/+subscriptions