mirror of
https://github.com/openvswitch/ovs
synced 2025-10-19 14:37:21 +00:00
cb54a8c576
For Windows, use a kernel assigned localhost TCP port to listen for runtime management connections and then write it into a file so that a client can read it and then make a TCP connection. Since we do not have the infrastructure to create pidfiles on windows as of now, we create the *.ctl file without a pid. This should be okay since we use different OVS_RUNDIR when we run multiple copies of a daemon. We do not generate man pages on Windows. But we still update them for Windows so that anyone can read it elsewhere. Since we do not generate it directly, we cannot dynamically show the configured OVS_RUNDIR in windows. So, I have a not so nice \fIOVS_RUNDIR\fR in the man page. Signed-off-by: Gurucharan Shetty <gshetty@nicira.com> Acked-by: Ben Pfaff <blp@nicira.com>
18 lines
834 B
Groff
18 lines
834 B
Groff
.IP "\fB\-\-unixctl=\fIsocket\fR"
|
|
Sets the name of the control socket on which \fB\*(PN\fR listens for
|
|
runtime management commands (see \fBRUNTIME MANAGEMENT COMMANDS\fR,
|
|
below). If \fIsocket\fR does not begin with \fB/\fR, it is
|
|
interpreted as relative to \fB@RUNDIR@\fR. If \fB\-\-unixctl\fR is
|
|
not used at all, the default socket is
|
|
\fB@RUNDIR@/\*(PN.\fIpid\fB.ctl\fR, where \fIpid\fR is \fB\*(PN\fR's
|
|
process ID.
|
|
.IP
|
|
On Windows, uses a kernel chosen TCP port on the localhost to listen
|
|
for runtime management commands. The kernel chosen TCP port value is written
|
|
in a file whose absolute path is pointed by \fIsocket\fR. If \fB\-\-unixctl\fR
|
|
is not used at all, the file is created as \fB\*(PN.ctl\fR in the configured
|
|
\fIOVS_RUNDIR\fR directory.
|
|
.IP
|
|
Specifying \fBnone\fR for \fIsocket\fR disables the control socket
|
|
feature.
|