group.of.nepali.translators team mailing list archive

[ChristianEhrhardt <1746081@xxxxxxxxxxxxxxxxxx>]

there is /etc/defaults/chrony in later versions of it.
But even that is no more working since the native systemd service does not consider it.

I might take a look into this for 18.04 to be correct, but atm I have no plan to do so for 16.04.
You might take a look at later Ubuntu releases and take the adapted init.d script and /etc/default/chrony to adapt your system as needed.

I guess we are even up for volunteers to do so for 16.04 - it just is
not on my personal tsak list.

** Also affects: chrony (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: chrony (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: chrony (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: chrony (Ubuntu)
       Status: New => Triaged

** Changed in: chrony (Ubuntu)
   Importance: Undecided => Medium

-- 
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:
  Triaged
Status in chrony source package in Xenial:
  Triaged

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