]>
Commit | Line | Data |
---|---|---|
da1af6e2 VA |
1 | <?xml version="1.0" encoding="utf-8"?> |
2 | <dl> | |
3 | <dt><code>--unixctl=<var>socket</var></code></dt> | |
4 | <dd> | |
5 | Sets the name of the control socket on which | |
6 | <code><var>program</var></code> listens for runtime management commands | |
7 | (see <var>RUNTIME MANAGEMENT COMMANDS,</var> below). If <var>socket</var> | |
8 | does not begin with <code>/</code>, it is interpreted as relative to | |
9 | <code>@RUNDIR@</code>. If <code>--unixctl</code> is not used at all, | |
10 | the default socket is | |
11 | <code>@RUNDIR@/<var>program</var>.</code><var>pid</var><code>.ctl</code>, | |
12 | where <var>pid</var> is <code><var>program</var></code>'s process ID. | |
13 | <p> | |
14 | On Windows a local named pipe is used to listen for runtime management | |
15 | commands. A file is created in the absolute path as pointed by | |
16 | <var>socket</var> or if <code>--unixctl</code> is not used at all, | |
17 | a file is created as <code><var>program</var></code> in the configured | |
18 | <var>OVS_RUNDIR</var> directory. The file exists just to mimic the | |
19 | behavior of a Unix domain socket. | |
20 | </p> | |
21 | <p> | |
22 | Specifying <code>none</code> for <var>socket</var> disables the control | |
23 | socket feature. | |
24 | </p> | |
25 | </dd> | |
26 | </dl> |