I just tested and it works perfectly, thanks.

On Fri, Jun 23, 2017 at 3:05 PM, Miroslav Lichvar <mlich...@redhat.com> wrote:
> On Fri, Jun 23, 2017 at 02:49:39PM -0400, Chris Perl wrote:
>> On Fri, Jun 23, 2017 at 2:43 PM, Miroslav Lichvar <mlich...@redhat.com> 
>> wrote:
>> > It's the patch included in the package from the copr repo. Does it not
>> > work for you?
>>
>> Oh, sorry that wasn't clear to me and I haven't had a chance to test
>> with it yet.
>>
>> Is there something included in the copr repo that isn't in the git
>> repo?  I'm not that familiar with copr, but based on what I have read,
>> I wouldn't think so.
>
> Yes, the copr package has a patch that's not included in the upstream
> chrony git repo. I don't want to include hacks specific to
> distribution's kernels.
>
> Here is the patch
>
> http://copr-dist-git.fedorainfracloud.org/cgit/mlichvar/chrony/chrony.git/tree/chrony-timestamping.patch
>
> It should apply to the current chrony git. For 3.1 it's necessary to
> add an extra argument to the two DEBUG_LOG calls.
>
> --
> Miroslav Lichvar
>
> --
> To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
> with "unsubscribe" in the subject.
> For help email chrony-users-requ...@chrony.tuxfamily.org
> with "help" in the subject.
> Trouble?  Email listmas...@chrony.tuxfamily.org.
>

-- 
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Reply via email to