I noticed the automatically generated reports about new commits from
g...@tuxfamily.net are no longer sent to this list for some reason. The
official repo is now on gitlab, but I'm still pushing to the original
repo as a mirror. I checked that the option is still enabled on the
tuxfamily repo
On Mon, Sep 11, 2023 at 16:46:07 +0200, Miroslav Lichvar wrote:
> On Mon, Sep 11, 2023 at 08:03:49AM -0400, Josef 'Jeff' Sipek wrote:
> > On Mon, Sep 11, 2023 at 10:29:30 +0200, Miroslav Lichvar wrote:
> > > That timestamp doesn't need much resolution. It just says when the
> > > offset (in double
On Wed, Sep 13, 2023 at 07:13:04AM -0400, Josef 'Jeff' Sipek wrote:
> Just to make sure I understand, the "proper" way is to adjust the offset to
> compensate for any rounding? IOW, something like what I had in my program
> before I messed with chrony's code:
>
> uint64_t sys; /* system
On Wed, Sep 13, 2023 at 15:52:26 +0200, Miroslav Lichvar wrote:
> On Wed, Sep 13, 2023 at 09:28:34AM -0400, Josef 'Jeff' Sipek wrote:
> > However, I also see that cooked_time (i.e., sys_ts+correction) is fed into
> > SPF_AccumulateSample as sample->time. Later on, combine_selected_samples
> >
On Wed, Sep 13, 2023 at 14:02:48 +0200, Miroslav Lichvar wrote:
> On Wed, Sep 13, 2023 at 07:13:04AM -0400, Josef 'Jeff' Sipek wrote:
> > Just to make sure I understand, the "proper" way is to adjust the offset to
> > compensate for any rounding? IOW, something like what I had in my program
> >
On Wed, Sep 13, 2023 at 09:28:34AM -0400, Josef 'Jeff' Sipek wrote:
> However, I also see that cooked_time (i.e., sys_ts+correction) is fed into
> SPF_AccumulateSample as sample->time. Later on, combine_selected_samples
> makes use of ->time to calculate various things. So, it looks like any
>
