| Re: [chrony-users] Chrony interface |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony interface
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 8 Jan 2020 09:53:43 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578473573; 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=TBNWB6PY2l8+wC86z2K56ZSPJcyirZYY97wqfDbPMVY=; b=K1jxJCWS6JjbuaBawc8YgWCIVAgiup4p9L/WfQcUkG9fzN22HTfvvmIk1uaj/ogB5YJa+y lbdcpIgAa1hR97HZ4Ke6jITsXdMumNpQ/9AlGUTaT0l1+thk8hVQf2+lpw4HWPYX66Sn7/ MkJVEOoqATXdfhng0hUnu86UssW5dsg=
On Tue, Jan 07, 2020 at 12:18:00PM +0000, Larsen, Simon wrote:
> I can make a system call to chronyc, read the output and parse it. Although I can't be sure the text output format won't change, so this does not seem like a good way to read the tracking/sources information from chronyc.
The format is not supposed to change, except new fields may be added
to the end of the report. There is the CSV mode (-c option) which
should make it easier for parsing.
> Have anybody accomplished this through better means? If so I would be very happy to hear from you!
You can write your own client. The protocol is quite simple. collectd
does that for instance.
The plan is to provide a library, which chronyc would be using, but
unfortunately there wasn't time to do that yet.
--
Miroslav Lichvar
--
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.