Hi there,
This seems like an appropriate change to me. If nobody object, I'm going
to apply this on the Debian side in the next few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068526
Title:
Hi Christian,
Could you please send the output of 'strace -o chrony_debug.txt --
chronyd -d -F -1'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915006
Title:
Consider merging 4.0-5 for Hirsute
Hi Thomas,
Please attach the output of 'systemctl status chrony' and 'chronyc
tracking'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880774
Title:
chronyd not synching time anymore since last up
@Christian - You won't encounter this problem on 64-bit architectures.
These *time64 system calls are dedicated to 32-bit ones to make them
Y2038-compatible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
chrony 3.5-9 now lands in Debian unstable with a fix (let’s hope) for this
issue.
The patch might need to be refreshed to apply cleanly on top of chrony
3.5-6ubuntu6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Thank you Robert.
So we will need to whitelist the clock_gettime64() system call in chronyd’s
seccomp filter.
I’ll send a patch upstream.
Meanwhile, you can disable the seccomp filter by running (as root):
# sed -i '/DAEMON_OPTS=/s/"-F -1"/"-F 0"/' /etc/default/chrony
# systemctl restart chrony.
Hey folks,
Sorry for my silence, I’m terribly busy lately…
Could you please install strace and run:
# strace -o /tmp/chronyd_debug.log chronyd -d -F -1
Then attach the output file (/tmp/chronyd_debug.log).
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Jason,
Could you please show us the output of 'systemctl status
chrony.service'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry pi 2
To ma
Christian, from what I remember chrony 3.2 needs [1] to render the
“smoothtime” test more reliable on some architectures. Could you please
give it a try?
[1]
https://git.tuxfamily.org/chrony/chrony.git/commit/?id=a4bd7f18000214ea4967a6a4d84a4a3e48d88a86
--
You received this bug notification beca
Hello Mark,
Debian chrony maintainer here.
So, this error occurs when attempting to rehabilitate systemd-timesyncd when
uninstalling/purging chrony (see restore_timesyncd() in d/postrm). This used
to be possible when systemd-timesyncd and chrony were co-installable but since
systemd 245.4-2{,ubu
10 matches
Mail list logo