| Re: [chrony-dev] Re: [chrony-users] Changing hostnames for chronyc sources and sourcestats results |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Re: [chrony-users] Changing hostnames for chronyc sources and sourcestats results
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Fri, 13 Dec 2019 09:51:51 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576227117; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uQTG2CWyXFivs62+tinIQe/QaGKsio1//a0g+RYnlM8=; b=BUC7lQ9W0hkTNOtebVx2VYoSCWsyVNvDQISP+XQhBuJNtjq4fO41FSTfwIvdjjSYJMLw6g 7LVaMWDaMpZseNq25Y3yRfP0wu2PwWWc6XOGUL94KjBcj/ynS3tUIv3Go6572rWfmi3wpR EHSrIkTFuuc9Z/X+stiXvUXfYLEFGI8=
On Thu, Dec 12, 2019 at 04:36:34PM -0600, Lonnie Abelbeck wrote:
> I ran across a couple little issues while testing.
>
> 1) startup errors for IPv6-related "Could not open ..." when built with --disable-ipv6 on a IPv6 capable system (long story).
Oh, I see. I'll fix that.
> 2) When building (cross-compiling via Buildroot) the install fails with "asciidoctor" not found. (BTW, asciidoctor is not installed)
> I'm not sure how this is different from chrony 3.5, but 3.5 builds fine.
This is only an issue when building from git, as there are no
pregenerated man pages, unlike in the released tarballs. As a
workaround you can run
touch doc/chrony{.conf,c,d}.man.in
> 3) Friendly reminder, additional chronyc tab completion entries ...
> * add "sourcename" to base_commands[]
> * add "pool" to add_options[]
Right, there is always something I forget.
Thanks for the testing and report.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.