| Re: [chrony-users] leapsectz and phc refclock offset |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] leapsectz and phc refclock offset
- From: Chris Perl <cperl@xxxxxxxxxxxxxx>
- Date: Tue, 26 Sep 2017 11:31:49 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=/oDnOwRZ5TZvBOpv955k9MptFbM2JUblve4JkIAn7e4=; b=h8LDrqgrS3IOBWOQyC5OG19LfvOzntRmk88ieSskJOtmIi+5h1IyclUVYaZMyh3LnW zpYvUyz2N8uESgtYkpLNIBpDNawMisSp0SkSzq0ofyvKB5WvGuOB+TOlaw3FTDt6DFRQ OpCGtQ6bnBm0aM7hNWR5KYNoQoEHf+JC6hZiI=
On Tue, Sep 26, 2017 at 11:26 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> You are the first one reporting this problem. If you have collected
> the phc2sys output and chrony's refclock+tracking logs from that time,
> I'd like to see that.
I don't have the output or logs handy, but I do have notes about how I
had the system configured, so I'll see if I can still reproduce the
issue and if I can, I'll get you the relevant info.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.