A running tinc daemon is listening on a UNIX socket. Other programs can connect
to this socket and send commands to control or query the running daemon. The
A running tinc daemon is listening on a UNIX socket. Other programs can connect
to this socket and send commands to control or query the running daemon. The
The daemon creates a PID file and a socket in `/var/run` normally (if
`./configure` has been run with `--localstatedir=/var`). They are called:
The daemon creates a PID file and a socket in `/var/run` normally (if
`./configure` has been run with `--localstatedir=/var`). They are called:
0 ^<cookie> 0
Where <cookie> must be replaced by the cookie value found in the PID file
created by the tinc daemon. This is the second word of the first line in
`/var/run/tinc.netname.pid`. Note, the `^` must still be put in front of the
0 ^<cookie> 0
Where <cookie> must be replaced by the cookie value found in the PID file
created by the tinc daemon. This is the second word of the first line in
`/var/run/tinc.netname.pid`. Note, the `^` must still be put in front of the
18 <type> <parameters...>
Where <type> is a numeric code that identifies the type of request, and
18 <type> <parameters...>
Where <type> is a numeric code that identifies the type of request, and
-<parameters> is a space-separated list of parameters. The available request
-types can be found in the `enum request_type` in `control_common.h`.
+<parameters> is a space-separated list of parameters. Individual parameters
+never contain spaces of their own. Consequently, no escaping is done. The
+available request types can be found in the `enum request_type` in
+`control_common.h`.