Debian Codegraph @

upstream/debian-unstable/man1/varlinkctl.1

raw
1 '\" t
2 .TH "VARLINKCTL" "1" "" "systemd 261~rc3" "varlinkctl"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 varlinkctl \- Introspect with and invoke Varlink services
24 .SH "SYNOPSIS"
25 .HP \w'\fBvarlinkctl\fR\ 'u
26 \fBvarlinkctl\fR [OPTIONS...] info \fIADDRESS\fR
27 .HP \w'\fBvarlinkctl\fR\ 'u
28 \fBvarlinkctl\fR [OPTIONS...] list\-interfaces \fIADDRESS\fR
29 .HP \w'\fBvarlinkctl\fR\ 'u
30 \fBvarlinkctl\fR [OPTIONS...] list\-methods \fIADDRESS\fR [\fIINTERFACE\fR...]
31 .HP \w'\fBvarlinkctl\fR\ 'u
32 \fBvarlinkctl\fR [OPTIONS...] introspect \fIADDRESS\fR [\fIINTERFACE\fR...]
33 .HP \w'\fBvarlinkctl\fR\ 'u
34 \fBvarlinkctl\fR [OPTIONS...] call \fIADDRESS\fR \fIMETHOD\fR [\fIARGUMENTS\fR]
35 .HP \w'\fBvarlinkctl\fR\ 'u
36 \fBvarlinkctl\fR [OPTIONS...] \-\-exec call \fIADDRESS\fR \fIMETHOD\fR \fIARGUMENTS\fR \-\- \fICMDLINE\fR
37 .HP \w'\fBvarlinkctl\fR\ 'u
38 \fBvarlinkctl\fR [OPTIONS...] serve \fIMETHOD\fR {\fICMDLINE\fR...}
39 .HP \w'\fBvarlinkctl\fR\ 'u
40 \fBvarlinkctl\fR [OPTIONS...] validate\-idl [\fIFILE\fR]
41 .SH "DESCRIPTION"
42 .PP
43 \fBvarlinkctl\fR
44 may be used to introspect and invoke
45 \m[blue]\fBVarlink\fR\m[]\&\s-2\u[1]\d\s+2
46 services\&.
47 .PP
48 Services are referenced by one of the following:
49 .sp
50 .RS 4
51 .ie n \{\
52 \h'-04'\(bu\h'+03'\c
53 .\}
54 .el \{\
55 .sp -1
56 .IP \(bu 2.3
57 .\}
58 A Varlink service reference starting with the
59 "unix:"
60 string, followed by an absolute
61 \fBAF_UNIX\fR
62 socket path, or by
63 "@"
64 and an arbitrary string (the latter for referencing sockets in the abstract namespace)\&. In this case, a stream socket connection is made to the specified socket\&.
65 .RE
66 .sp
67 .RS 4
68 .ie n \{\
69 \h'-04'\(bu\h'+03'\c
70 .\}
71 .el \{\
72 .sp -1
73 .IP \(bu 2.3
74 .\}
75 A Varlink service reference starting with the
76 "exec:"
77 string, followed by an absolute path of a binary to execute\&. In this case, the specified process is forked off locally, with a connected stream socket passed in\&.
78 .RE
79 .sp
80 .RS 4
81 .ie n \{\
82 \h'-04'\(bu\h'+03'\c
83 .\}
84 .el \{\
85 .sp -1
86 .IP \(bu 2.3
87 .\}
88 A Varlink service reference starting with the
89 "ssh\-unix:"
90 string, followed by an SSH host specification, followed by
91 ":", followed by an absolute
92 \fBAF_UNIX\fR
93 socket path\&. (This requires OpenSSH 9\&.4 or newer on the server side, and abstract namespace sockets are not supported\&.)
94 .RE
95 .sp
96 .RS 4
97 .ie n \{\
98 \h'-04'\(bu\h'+03'\c
99 .\}
100 .el \{\
101 .sp -1
102 .IP \(bu 2.3
103 .\}
104 A Varlink service reference starting with the
105 "ssh\-exec:"
106 string, followed by an SSH host specification, followed by
107 ":", followed by a command line\&. In this case, the command is invoked and the Varlink protocol is spoken on the standard input and output of the invoked command\&.
108 .RE
109 .PP
110 For convenience, these two simpler (redundant) service address syntaxes are also supported:
111 .sp
112 .RS 4
113 .ie n \{\
114 \h'-04'\(bu\h'+03'\c
115 .\}
116 .el \{\
117 .sp -1
118 .IP \(bu 2.3
119 .\}
120 A file system path to an
121 \fBAF_UNIX\fR
122 socket, either absolute (i\&.e\&. begins with
123 "/") or relative (in which case it must begin with
124 "\&./")\&.
125 .RE
126 .sp
127 .RS 4
128 .ie n \{\
129 \h'-04'\(bu\h'+03'\c
130 .\}
131 .el \{\
132 .sp -1
133 .IP \(bu 2.3
134 .\}
135 A file system path to an executable, either absolute or relative (as above, must begin with
136 "/"
137 or
138 "\&./", respectively)\&.
139 .RE
140 .SH "COMMANDS"
141 .PP
142 The following commands are understood:
143 .PP
144 \fBinfo\fR \fIADDRESS\fR
145 .RS 4
146 Shows brief information about the specified service, including vendor name and list of implemented interfaces\&. Expects a service address in one of the formats described above\&.
147 .sp
148 Added in version 255\&.
149 .RE
150 .PP
151 \fBlist\-interfaces\fR \fIADDRESS\fR
152 .RS 4
153 Shows a list of interfaces implemented by the specified service\&. Expects a service address in one of the formats described above\&.
154 .sp
155 Added in version 255\&.
156 .RE
157 .PP
158 \fBlist\-methods\fR \fIADDRESS\fR [\fIINTERFACE\&...\fR]
159 .RS 4
160 Shows a list of methods implemented by the specified service\&. Expects a service address in one of the formats described above as well as one or more interface names\&. If no interface name is specified, lists all methods of all interfaces implemented by the service, otherwise just the methods in the specified interfaces\&.
161 .sp
162 Added in version 257\&.
163 .RE
164 .PP
165 \fBintrospect\fR \fIADDRESS\fR [\fIINTERFACE\&...\fR]
166 .RS 4
167 Shows the interface definitions of the specified interfaces provided by the specified service\&. Expects a service address in one of the formats described above and optionally one or more Varlink interface names\&. If no interface names are specified, shows all provided interfaces by the service\&.
168 .sp
169 Added in version 255\&.
170 .RE
171 .PP
172 \fBcall\fR \fIADDRESS\fR \fIMETHOD\fR [\fIARGUMENTS\fR]
173 .RS 4
174 Calls the specified method of the specified service\&. Expects a service address in the format described above, a fully qualified Varlink method name, and a JSON arguments object\&. If the arguments object is not specified, it is read from STDIN instead\&. To pass an empty list of parameters, specify the empty object
175 "{}"\&.
176 .sp
177 The reply parameters are written as JSON objects to STDOUT\&.
178 .sp
179 Added in version 255\&.
180 .RE
181 .PP
182 \fBserve\fR \fIMETHOD\fR \fICMDLINE\&...\fR
183 .RS 4
184 Run a Varlink server that accepts protocol upgrade requests for the specified method and connects the upgraded connection to the standard input and output of the specified command\&. This can act as a server\-side counterpart to
185 \fBcall\fR
186 \fB\-\-upgrade\fR\&.
187 .sp
188 The listening socket must be passed via socket activation (i\&.e\&. the
189 \fI$LISTEN_FDS\fR
190 protocol), making this command suitable for use in socket\-activated service units\&. When a client calls the specified method with the upgrade flag, the server sends a reply confirming the upgrade, then forks and executes the given command line with the upgraded connection on its standard input and output\&.
191 .sp
192 This effectively turns any command that speaks a protocol over standard input/output into a Varlink service, discoverable via the service registry and authenticated via socket credentials\&. Because each connection is handled by a forked child process, the service unit can apply systemd\*(Aqs sandboxing options (such as
193 \fIProtectSystem=\fR, etc\&.) and does not operate in the caller\*(Aqs environment\&.
194 .sp
195 Added in version 261\&.
196 .RE
197 .PP
198 \fBlist\-registry\fR
199 .RS 4
200 Shows a list of Varlink services currently registered in the service registry, plus their entrypoint sockets\&. (Currently, this simply enumerates the sockets and symlinked sockets in
201 /run/varlink/registry/, see below\&.)
202 .sp
203 Added in version 260\&.
204 .RE
205 .PP
206 \fBvalidate\-idl\fR [\fIFILE\fR]
207 .RS 4
208 Reads a Varlink interface definition file, parses and validates it, then outputs it with syntax highlighting\&. This checks for syntax and internal consistency of the interface\&. Expects a file name to read the interface definition from\&. If omitted, reads the interface definition from STDIN\&.
209 .sp
210 Added in version 255\&.
211 .RE
212 .PP
213 \fBhelp\fR
214 .RS 4
215 Shows command syntax help\&.
216 .sp
217 Added in version 255\&.
218 .RE
219 .SH "OPTIONS"
220 .PP
221 The following options are understood:
222 .PP
223 \fB\-\-more\fR
224 .RS 4
225 When used with
226 \fBcall\fR: expect multiple method replies\&. If this flag is set, the method call is sent with the
227 \fBmore\fR
228 flag set, which tells the service to generate multiple replies, if needed\&. The command remains running until the service sends a reply message that indicates it is the last in the series (or if the configured timeout is reached, see below)\&. This flag should be set only for method calls that support this mechanism\&.
229 .sp
230 If this mode is enabled, output is automatically switched to JSON\-SEQ mode, so that individual reply objects can be easily discerned\&.
231 .sp
232 This switch has no effect on the method call timeout applied by default\&. Regardless of whether
233 \fB\-\-more\fR
234 is specified or not, the default timeout will be 45s\&. Use
235 \fB\-\-timeout=\fR
236 (see below) to change or disable the timeout\&. When invoking a method call that continuously returns updates, it is typically desirable to disable the timeout with
237 \fB\-\-timeout=infinity\fR\&. On the other hand, when invoking a
238 \fB\-\-more\fR
239 method call for the purpose of enumerating objects (which likely will complete quickly), it is typically beneficial to leave the timeout logic enabled, for robustness reasons\&.
240 .sp
241 Added in version 255\&.
242 .RE
243 .PP
244 \fB\-E\fR
245 .RS 4
246 A shortcut for
247 \fB\-\-more \-\-timeout=infinity\fR\&. This switch is useful for method calls that implement subscription to a continuous stream of updates\&.
248 .sp
249 Added in version 257\&.
250 .RE
251 .PP
252 \fB\-\-collect\fR
253 .RS 4
254 This is similar to
255 \fB\-\-more\fR, but collects all responses in a JSON array, and prints it, rather than in JSON\-SEQ mode\&.
256 .sp
257 Added in version 256\&.
258 .RE
259 .PP
260 \fB\-\-oneway\fR
261 .RS 4
262 When used with
263 \fBcall\fR: do not expect a method reply\&. If this flag is set, the method call is sent with the
264 \fBoneway\fR
265 flag set (the command exits immediately after), which tells the service not to generate a reply\&.
266 .sp
267 Added in version 255\&.
268 .RE
269 .PP
270 \fB\-\-upgrade\fR
271 .RS 4
272 When used with
273 \fBcall\fR: request a protocol upgrade\&. The method call is sent with the
274 \fBupgrade\fR
275 flag set\&. The service is expected to send a single reply confirming the upgrade\&. After the reply, the Varlink protocol is no longer in effect on the connection\&.
276 .sp
277 If
278 \fB\-\-exec\fR
279 is not specified,
280 \fBvarlinkctl\fR
281 acts as a bidirectional proxy: data read from standard input is forwarded to the upgraded connection, and data received from the connection is written to standard output\&.
282 .sp
283 If
284 \fB\-\-exec\fR
285 is specified, the upgraded connection socket is placed on both standard input and standard output of the invoked process\&. This is similar to the regular
286 \fB\-\-exec\fR
287 behavior (without
288 \fB\-\-upgrade\fR), which places the method call reply on standard input\&. The invoked process can thus simply read from and write to stdin/stdout to communicate over the upgraded protocol\&.
289 .sp
290 This option may not be combined with
291 \fB\-\-more\fR,
292 \fB\-\-oneway\fR,
293 \fB\-\-collect\fR,
294 \fB\-\-graceful=\fR, or
295 \fB\-\-push\-fd=\fR\&.
296 .sp
297 Added in version 261\&.
298 .RE
299 .PP
300 \fB\-\-json=\fR\fB\fIMODE\fR\fR
301 .RS 4
302 Selects the JSON output formatting, either
303 "pretty"
304 for nicely indented, colorized output, or
305 "short"
306 for terse output with minimal whitespace and no newlines\&. Defaults to
307 "short"\&.
308 .sp
309 Added in version 255\&.
310 .RE
311 .PP
312 \fB\-j\fR
313 .RS 4
314 Equivalent to
315 \fB\-\-json=pretty\fR
316 when invoked interactively from a terminal\&. Otherwise, it is equivalent to
317 \fB\-\-json=short\fR, in particular when the output is piped to some other program\&.
318 .sp
319 Added in version 255\&.
320 .RE
321 .PP
322 \fB\-\-quiet\fR, \fB\-q\fR
323 .RS 4
324 Suppress output of method call replies\&.
325 .sp
326 Added in version 257\&.
327 .RE
328 .PP
329 \fB\-\-graceful=\fR
330 .RS 4
331 Takes a qualified Varlink error name, i\&.e\&. an interface name, suffixed by an error name, separated by a dot, e\&.g\&.
332 "org\&.varlink\&.service\&.InvalidParameter"\&. Ensures that, if a method call fails with the specified error, this will be treated as success, i\&.e\&. will cause the
333 \fBvarlinkctl\fR
334 invocation to exit with a zero exit status\&. This option may be used more than once in order to treat multiple different errors as successes\&.
335 .sp
336 Added in version 257\&.
337 .RE
338 .PP
339 \fB\-\-timeout=\fR
340 .RS 4
341 Expects a timeout in seconds as parameter\&. By default, a timeout of 45s is enforced\&. To turn off the timeout, specify
342 "infinity"
343 or an empty string\&.
344 .sp
345 Added in version 257\&.
346 .RE
347 .PP
348 \fB\-\-exec\fR
349 .RS 4
350 Once the method call issued via
351 \fBcall\fR
352 completed successfully, chainload the specified command line, with the method call output parameters serialized to JSON passed into standard input (and standard output and standard error inherited from the invoking process)\&. Moreover any file descriptors passed back on the underlying communication socket are passed to the invoked process via the usual
353 \fI$LISTEN_FDS\fR
354 protocol\&. This functionality may be used to consume replies that come with associated file descriptors in a reasonable way\&.
355 .sp
356 Now that if
357 \fB\-\-exec\fR
358 is specified the the third parameter to
359 \fBcall\fR
360 is not optional (i\&.e\&. the method call parameters)\&.
361 .sp
362 Added in version 258\&.
363 .RE
364 .PP
365 \fB\-\-push\-fd=\fR
366 .RS 4
367 Takes a numeric file descriptor number as parameter\&. May be used to pass a file descriptor along with the method call, if the underlying transport supports this\&. May be used multiple times to pass multiple file descriptors, retaining the order in which they are specified\&. The specified file descriptors must be passed to the
368 \fBvarlinkctl\fR
369 invocation\&. Optionally, in place of a numeric file descriptor number an absolute or relative file system path (the latter must be prefixed with
370 "\&./") may be specified, which is opened in read\-only mode\&.
371 .sp
372 Added in version 258\&.
373 .RE
374 .PP
375 \fB\-\-system\fR, \fB\-\-user\fR
376 .RS 4
377 Determines whether to query to the per\-system or per\-user registry when using the
378 \fBlist\-registry\fR
379 command\&. By default, the per\-system registry is queried\&.
380 .PP
381 Added in version 260\&.
382 .RE
383 .PP
384 \fB\-\-no\-ask\-password\fR
385 .RS 4
386 Do not query the user for authentication for privileged operations\&.
387 .RE
388 .PP
389 \fB\-\-no\-pager\fR
390 .RS 4
391 Do not pipe output into a pager\&.
392 .RE
393 .PP
394 \fB\-h\fR, \fB\-\-help\fR
395 .RS 4
396 Print a short help text and exit\&.
397 .RE
398 .PP
399 \fB\-\-version\fR
400 .RS 4
401 Print a short version string and exit\&.
402 .RE
403 .SH "FILES & DIRECTORIES"
404 .PP
405 /run/varlink/registry/
406 .RS 4
407 Directory containing
408 \fBAF_UNIX\fR
409 entrypoint socket inodes (or symlinks to them) of well\-known, public Varlink interfaces on the local system\&. They are named after the Varlink interface they implement\&.
410 .sp
411 Use
412 \fBvarlinkctl list\-registry\fR
413 to show the contents of this directory\&.
414 .sp
415 (Inodes that neither qualify as socket inodes nor as symlinks to them shall be ignored\&. A future extension might introduce regular files and directories to enhance the registry functionality\&.)
416 .sp
417 Added in version 260\&.
418 .RE
419 .SH "EXAMPLES"
420 .PP
421 \fBExample\ \&1.\ \&Investigating a Service\fR
422 .PP
423 The following three commands inspect the
424 "io\&.systemd\&.Resolve"
425 service implemented by
426 \fBsystemd-resolved.service\fR(8), listing general service information and implemented interfaces, and then displaying the interface definition of its primary interface:
427 .sp
428 .if n \{\
429 .RS 4
430 .\}
431 .nf
432 $ varlinkctl info /run/systemd/resolve/io\&.systemd\&.Resolve
433 Vendor: The systemd Project
434 Product: systemd (systemd\-resolved)
435 Version: 254 (254\-1522\-g4790521^)
436 URL: https://systemd\&.io/
437 Interfaces: io\&.systemd
438 io\&.systemd\&.Resolve
439 org\&.varlink\&.service
440 $ varlinkctl list\-interfaces /run/systemd/resolve/io\&.systemd\&.Resolve
441 io\&.systemd
442 io\&.systemd\&.Resolve
443 org\&.varlink\&.service
444 $ varlinkctl introspect /run/systemd/resolve/io\&.systemd\&.Resolve io\&.systemd\&.Resolve
445 interface io\&.systemd\&.Resolve
446 type ResolvedAddress(
447 ifindex: ?int,
448 \&...
449 .fi
450 .if n \{\
451 .RE
452 .\}
453 .PP
454 (Interface definition has been truncated in the example above, in the interest of brevity\&.)
455 .PP
456 \fBExample\ \&2.\ \&Invoking a Method\fR
457 .PP
458 The following command resolves a hostname via
459 \fBsystemd-resolved.service\fR(8)\*(Aqs
460 \fBResolveHostname\fR
461 method call\&.
462 .sp
463 .if n \{\
464 .RS 4
465 .\}
466 .nf
467 $ varlinkctl call /run/systemd/resolve/io\&.systemd\&.Resolve io\&.systemd\&.Resolve\&.ResolveHostname \*(Aq{"name":"systemd\&.io","family":2}\*(Aq \-j
468 {
469 "addresses" : [
470 {
471 "ifindex" : 2,
472 "family" : 2,
473 "address" : [
474 185,
475 199,
476 111,
477 153
478 ]
479 }
480 ],
481 "name" : "systemd\&.io",
482 "flags" : 1048577
483 }
484 .fi
485 .if n \{\
486 .RE
487 .\}
488 .PP
489 \fBExample\ \&3.\ \&Investigating a Service Executable\fR
490 .PP
491 The following command inspects the
492 /usr/lib/systemd/systemd\-pcrextend
493 executable and the IPC APIs it provides\&. It then invokes a method on it:
494 .sp
495 .if n \{\
496 .RS 4
497 .\}
498 .nf
499 # varlinkctl info /usr/lib/systemd/systemd\-pcrextend
500 Vendor: The systemd Project
501 Product: systemd (systemd\-pcrextend)
502 Version: 254 (254\-1536\-g97734fb)
503 URL: https://systemd\&.io/
504 Interfaces: io\&.systemd
505 io\&.systemd\&.PCRExtend
506 org\&.varlink\&.service
507 # varlinkctl introspect /usr/lib/systemd/systemd\-pcrextend io\&.systemd\&.PCRExtend
508 interface io\&.systemd\&.PCRExtend
509
510 method Extend(
511 pcr: int,
512 text: ?string,
513 data: ?string
514 ) \-> ()
515 # varlinkctl call /usr/lib/systemd/systemd\-pcrextend io\&.systemd\&.PCRExtend\&.Extend \*(Aq{"pcr":15,"text":"foobar"}\*(Aq
516 {}
517 .fi
518 .if n \{\
519 .RE
520 .\}
521 .PP
522 \fBExample\ \&4.\ \&Invoking a method remotely via SSH\fR
523 .PP
524 The following command acquires a report about the identity of a remote host
525 "somehost"
526 from
527 \fBsystemd-hostnamed.service\fR(8)
528 by connecting via SSH to the
529 \fBAF_UNIX\fR
530 socket the service listens on:
531 .sp
532 .if n \{\
533 .RS 4
534 .\}
535 .nf
536 # varlinkctl call ssh\-unix:somehost:/run/systemd/io\&.systemd\&.Hostname io\&.systemd\&.Hostname\&.Describe \*(Aq{}\*(Aq
537 .fi
538 .if n \{\
539 .RE
540 .\}
541 .PP
542 To invoke a Varlink service binary directly on the remote host, rather than talking to a service via
543 \fBAF_UNIX\fR
544 can be done like this:
545 .sp
546 .if n \{\
547 .RS 4
548 .\}
549 .nf
550 # varlinkctl call ssh\-exec:somehost:systemd\-creds org\&.varlink\&.service\&.GetInfo \*(Aq{}\*(Aq
551 .fi
552 .if n \{\
553 .RE
554 .\}
555 .PP
556 \fBExample\ \&5.\ \&Serving a Sandboxed Decompressor via Protocol Upgrade\fR
557 .PP
558 The following socket and service units expose
559 \fBxz\fR
560 decompression as a Varlink service\&. Clients connect and send compressed data over the upgraded connection, receiving decompressed output in return\&.
561 .sp
562 .if n \{\
563 .RS 4
564 .\}
565 .nf
566 # /etc/systemd/system/varlink\-decompress\-xz\&.socket
567 [Socket]
568 ListenStream=/run/varlink/registry/com\&.example\&.Decompress\&.XZ
569
570 [Install]
571 WantedBy=sockets\&.target
572
573 # /etc/systemd/system/varlink\-decompress\-xz\&.service
574 [Service]
575 ExecStart=varlinkctl serve com\&.example\&.Decompress\&.XZ xz \-d
576 DynamicUser=yes
577 PrivateNetwork=yes
578 ProtectSystem=strict
579 ProtectHome=yes
580 NoNewPrivileges=yes
581 SystemCallFilter=~@privileged @resources
582 MemoryMax=256M
583 .fi
584 .if n \{\
585 .RE
586 .\}
587 .PP
588 A client can then decompress data through this service:
589 .sp
590 .if n \{\
591 .RS 4
592 .\}
593 .nf
594 $ echo "hello" | xz | varlinkctl call \-\-upgrade \e
595 unix:/run/varlink/registry/com\&.example\&.Decompress\&.XZ \e
596 com\&.example\&.Decompress\&.XZ \*(Aq{}\*(Aq
597 hello
598 .fi
599 .if n \{\
600 .RE
601 .\}
602 .PP
603 For quick testing without unit files,
604 \fBsystemd\-socket\-activate\fR
605 can be used to provide the listening socket:
606 .sp
607 .if n \{\
608 .RS 4
609 .\}
610 .nf
611 $ systemd\-socket\-activate \-l /tmp/decompress\&.sock \-\- varlinkctl serve com\&.example\&.Decompress\&.XZ xz \-d &
612 $ echo "hello" | xz | varlinkctl call \-\-upgrade unix:/tmp/decompress\&.sock com\&.example\&.Decompress\&.XZ \*(Aq{}\*(Aq
613 hello
614 .fi
615 .if n \{\
616 .RE
617 .\}
618 .SH "SEE ALSO"
619 .PP
620 \fBbusctl\fR(1), \m[blue]\fBVarlink\fR\m[]\&\s-2\u[1]\d\s+2
621 .SH "NOTES"
622 .IP " 1." 4
623 Varlink
624 .RS 4
625 \%https://varlink.org/
626 .RE