mir/ovs
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-08-22 09:58:01 +00:00
Code Issues Releases Wiki Activity
ovs/lib/unixctl.man

18 lines
847 B
Groff
Raw Normal View History

ovsdb-server: Document --unixctl option.
2010-03-23 11:22:42 -07:00
.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.
unixctl: Add support for Windows. 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>
2014-03-28 08:19:59 -07:00
.IP
Windows: Local named pipe implementation Currently in the case of command line arguments punix/unix, on Windows we create a file, write a TCP port number to connect. This is a security concern. This patch adds support for the command line arguments punix/unix trying to mimic AF_UNIX behind a local named pipe. This patch drops the TCP socket implementation behind command line arguments punix/unix and switches to the local named pipe implementation. Since we do not write anything to the file created by the punix/unix arguments, switch tests to plain file existence. Man pages and code comments have been updated. Signed-off-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com> Acked-by: Paul Boca <pboca@cloudbasesolutions.com> Signed-off-by: Gurucharan Shetty <guru@ovn.org>
2016-08-02 18:19:34 +00:00
On Windows a local named pipe is used to listen for runtime management
commands. A file is created in the absolute path as pointed by
\fIsocket\fR or if \fB\-\-unixctl\fR is not used at all, a file is
created as \fB\*(PN.ctl\fR in the configured \fIOVS_RUNDIR\fR
directory. The file exists just to mimic the behavior of a Unix domain socket.
unixctl: Add support for Windows. 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>
2014-03-28 08:19:59 -07:00
.IP
Add new "dummy" netdev and dpif implementations for use in unit tests.
2010-11-29 12:21:08 -08:00
Specifying \fBnone\fR for \fIsocket\fR disables the control socket
feature.
Reference in New Issue Copy Permalink