Ubuntu
chrony package

Daemon flags aren't supported ? or unclear how.

Bug #1746081 reported by James
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chrony (Debian)
Fix Released
Unknown
chrony (Ubuntu)
Fix Released
Medium
Christian Ehrhardt 
Xenial
Triaged
Wishlist
Unassigned

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!

Tags: xenial
Hans Joachim Desserud (hjd)
tags: added: xenial
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

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.

Changed in chrony (Ubuntu Xenial):
status: New → Triaged
importance: Undecided → Wishlist
Changed in chrony (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Christian Ehrhardt  (paelzer)
Changed in chrony (Ubuntu):
status: Triaged → In Progress
assignee: nobody → ChristianEhrhardt (paelzer)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Tested proposed fix on test ppa https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3115/+packages working fine picking up DAEMON_OPTS from /etc/default/chrony now.

(Also safe against no option set or removed file.

Revision history for this message
James (k-james-d) wrote :

Thanks for checking this out! I'll look at your fix and incorporate similar.

Bug Watch Updater (bug-watch-updater)
Changed in chrony (Debian):
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in chrony (Debian):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Fri, 19 Jan 2018 09:45:38 +0100

Changed in chrony (Ubuntu):
status: In Progress → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in chrony (Debian):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.