This bug was fixed in the package chrony - 3.5.1-1ubuntu2
---
chrony (3.5.1-1ubuntu2) groovy; urgency=medium
* d/chronyd-starter.sh: fix commandline argument parsing (LP:
#1898000)
-- Christian Ehrhardt Tue, 06 Oct
2020 12:20:40 +0200
** Changed in: chrony (Ubuntu)
Uploaded to groovy and not requiring an FFe (since it is a small and pure fix).
Never the less it will wait a bit until the release Team approves it since we
are in Freeze for 20.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/391867
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898000
Title:
bogus handling of
** Changed in: chrony (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898000
Title:
bogus handling of DAEMON_OPTS by chronyd-starter.sh
To manage
As mentioned we use getopt ignoring all but -x to select.
opstring so far was ":x"
1. leading ":" => silence errors
2. look for -x
We had hoped that we don't have to "keep track" of the official chronyd
arguments that way.
But what happens is that the "1" as argument to -F with an optstring
Thanks Simon, I missed that little detail when retrying.
I now can confirm.
The impact is gladly rather low as it makes one "-x" to two "-x -x"
which should not change the behavior of chronyd.
For the time being anyone affected that sets "-x" manually in
/etc/default/chrony and want to avoid
Hello Christian,
One need to use "-F 1 -x" in order to reproduce. The "1" instead of "-1"
is what causes the bug to happen. Thanks!
Regards,
Simon
On 2020-10-05 7:33 a.m., Christian Ehrhardt wrote:
> Hrm I got to test this now and I can't reproduce with:
>
> Groovy
> root@g:~# grep OPT
Hrm I got to test this now and I can't reproduce with:
Groovy
root@g:~# grep OPT /etc/default/chrony
DAEMON_OPTS="-F -1 -x"
root@g:~# systemctl restart chrony; systemctl status chrony | grep
'sbin\/chronyd'
├─118154 /usr/sbin/chronyd -F -1 -x
└─118155 /usr/sbin/chronyd
Hi Simon,
you are right and this is a valid bug for sure.
Yet I have a very busy week ahead - it might take some time ... :-/
** Tags added: server-next
** Changed in: chrony (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because
