Daemon flags aren't supported ? or unclear how.
Bug #1746081 reported by
James
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: | added: xenial |
Changed in chrony (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → ChristianEhrhardt (paelzer) |
Changed in chrony (Debian): | |
status: | Unknown → New |
Changed in chrony (Debian): | |
status: | New → Fix Committed |
Changed in chrony (Debian): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.