Hi chrony-dev,
chrony is tested in Debian/Ubuntu on any update of related packages
and while that was running I found that arm64 and ppc64 reproducibly
hang [1][2]. OTOH arm64 and s390x reproducibly work.
Unfortunately the tests do not leave any reasonable debug output, the tests run:
debian/t
Hi Christian,
On 2019-12-06T10:21+0100, Christian Ehrhardt wrote:
Hi chrony-dev,
chrony is tested in Debian/Ubuntu on any update of related packages
and while that was running I found that arm64 and ppc64 reproducibly
hang [1][2]. OTOH arm64 and s390x reproducibly work.
^
On Fri, Dec 6, 2019 at 11:32 AM Vincent Blut wrote:
>
> Hi Christian,
>
> On 2019-12-06T10:21+0100, Christian Ehrhardt wrote:
> >Hi chrony-dev,
> >chrony is tested in Debian/Ubuntu on any update of related packages
> >and while that was running I found that arm64 and ppc64 reproducibly
> >hang [1]
On Fri, Dec 6, 2019 at 11:32 AM Vincent Blut wrote:
>
> Hi Christian,
>
> On 2019-12-06T10:21+0100, Christian Ehrhardt wrote:
> >Hi chrony-dev,
> >chrony is tested in Debian/Ubuntu on any update of related packages
> >and while that was running I found that arm64 and ppc64 reproducibly
> >hang [1]
> >
> > Could that be due to the use of “-x”? IFAIR you have extra stuff on
> > Ubuntu about that option.
>
> I was testing the current master tarball from upstream to avoid any confusion.
> => https://git.tuxfamily.org/chrony/chrony.git/snapshot/chrony-master.tar.gz
>
> That exposes the same behav
On 2019-12-06T12:35+0100, Christian Ehrhardt wrote:
>
> Could that be due to the use of “-x”? IFAIR you have extra stuff on
> Ubuntu about that option.
I was testing the current master tarball from upstream to avoid any confusion.
=> https://git.tuxfamily.org/chrony/chrony.git/snapshot/chrony-ma
On Fri, Dec 6, 2019 at 12:51 PM Vincent Blut wrote:
>
> On 2019-12-06T12:35+0100, Christian Ehrhardt wrote:
> >> >
> >> > Could that be due to the use of “-x”? IFAIR you have extra stuff on
> >> > Ubuntu about that option.
> >>
> >> I was testing the current master tarball from upstream to avoid a
On 2019-12-06T10:21+0100, Christian Ehrhardt wrote:
Hi chrony-dev,
chrony is tested in Debian/Ubuntu on any update of related packages
and while that was running I found that arm64 and ppc64 reproducibly
hang [1][2]. OTOH arm64 and s390x reproducibly work.
By the way, I just gave it a shot on a
On 2019-12-06T16:55+0100, Vincent Blut wrote:
On 2019-12-06T10:21+0100, Christian Ehrhardt wrote:
Hi chrony-dev,
chrony is tested in Debian/Ubuntu on any update of related packages
and while that was running I found that arm64 and ppc64 reproducibly
hang [1][2]. OTOH arm64 and s390x reproducibly
macOS seems to have two clocks:
• a hardware clock, which always runs (even if the device is switched off)
• and a software clock, which is used by all apps.
When the device starts (or awakes from sleep) the software clock is set from
the hardware clock.
The problem: adjtime (or whatever chronyd
10 matches
Mail list logo