From 9df5902e8cdf9d7f13e9da9f7045a182c1704a01 Mon Sep 17 00:00:00 2001 From: Robert Günzler Date: Thu, 23 Oct 2025 16:29:21 +0200 Subject: varlink: edit MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Robert Günzler --- src/inc/varlink.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'src/inc/varlink.md') diff --git a/src/inc/varlink.md b/src/inc/varlink.md index bb65dea..9465efe 100644 --- a/src/inc/varlink.md +++ b/src/inc/varlink.md @@ -4,7 +4,8 @@ combines them with simple standard tools/technologies in the form of unix sockets and JSON. For C, there is a library by [emersion][2] called vali, which does pretty much -all you need to get going: https://emersion.fr/blog/2025/announcing-vali/ +everything all you need to get going: +https://emersion.fr/blog/2025/announcing-vali/ When you have written your service, here is how to interact with it just using standard utils, socat and jq: @@ -31,7 +32,7 @@ cat <<-EOF | jq --raw-output0 | socat STDIO UNIX-CONNECT:"$SOCKET" | jq EOF ``` -This will return the service interface (if the service listening at the socket +This will return the service interface, if the service listening at the socket actually implements it. Note the use of `jq --raw-output0`. It is possible to omit the jq invocations, -- cgit 1.4.1