| Re: [chrony-dev] libchrony |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] libchrony
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Sat, 3 Jun 2023 10:48:33 +1200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smtpservice.net; i=@smtpservice.net; q=dns/txt; s=a1-4; t=1685746133; h=feedback-id : x-smtpcorp-track : date : message-id : to : subject : from : reply-to : sender : list-unsubscribe; bh=uo9z25xYem/cSVeCRzM5eIas1csynJGQeN8llSP/mYM=; b=F7P9OvKo+hvkJ8xwBeyv8LuztkNBFEpoX8niVmgCkB/JCWklqNTprcVXVfstlUtjh2NA5 pWTemT3apRXchWcDErVhqAMyhQzZbNcfm8IxNK3vqV1bocr/8O74PgAV5Qi8y+PabsE3+un bBpNtBz3EsYde9u7BuBCyGjjEXIyRRliJEbxeIqZwjYZbM7/WBI8bcPfE0EIrmygdNJXBaG HRDvb9mzn1ulf2UCvrf6Sl0NdZASXpfzyrnCsJ4/3+s6WFkbBJULSQkbVNLJTpR53a/xM3S trgZcxN0lbJnfGgKH7FDnmGbpnZ4bRK0bPE1kGmKcH8COyuAgn27YyzI1iXQ==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=whatroute.net; i=@whatroute.net; q=dns/txt; s=s149811; t=1685746133; h=from : subject : to : message-id : date; bh=uo9z25xYem/cSVeCRzM5eIas1csynJGQeN8llSP/mYM=; b=aE6ReF8NRQ1ZOvqIADCF25GHef+8KhIOlAQK0LLm4qaMvCRoOPRWzFdFsUcq4NbuffnZq Qnre19jkMOCa8QFVP2Eh4HekdOz8tYD5NyqnXHjypEgf6LEeZsjZuX4imQRqmkFtOa9T8K6 RY5EGiukg2WnNGiumrN6bpNrBjSHQRci5l/qFq24uzRWR+Q3OoRYfb1lisdqlxcEm09ztuL +rXtGOdmyoR7c84NhZ6v0YDNITjGa3oKccMOimoJpeEaX7gmhi5t1GEtjSNPdQLNZmQbQef 0PKgOwjXzpPQ0EBJcpJOhOzlDpQxlDPh5HoSys8/BUNaTf0xBVd1zOUz9tIA==
Ho Miroslav
I presume that chronyc will eventually use this library.
If/when that happens I would like to see an option to compile the library as a static library and with the option to build chronyc with static linkage.
This would avoid all sorts of dependency issues for me in in running chronyc/chronyd on multiple versions of macOS.
The interfaces so far look good to me.
Thank you for all your work.
Bryan
> On 1/06/2023, at 2:51 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>
> I started the new project for chronyd monitoring and management
> library that was discussed here recently.
>
> https://gitlab.com/chrony/libchrony
>
> Basically, it's a low level library for sending and receiving cmdmon
> messages with access to individual fields. Currently, it's monitoring
> only and only some reports are supported. Other reports and commands
> could be added later if there is interest.
>
> At this point I'm mainly interested in feedback about the API, if it
> looks sane and future proof.
>
> --
> 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.
>
Bryan Christianson
bryan@xxxxxxxxxxxxx
--
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.