X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=utilities%2Fovs-ctl.8;h=04c2930585cab183629e4d0b7e3ce95d5796f7de;hb=6ed3b860fe806fce26dfc760cb428a9a5432d329;hp=06ccfecac03a58937453e8df53a140cbabac9f7b;hpb=9b80f761bed9a32c1b0eb22ee3361966057ea973;p=openvswitch diff --git a/utilities/ovs-ctl.8 b/utilities/ovs-ctl.8 index 06ccfeca..04c29305 100644 --- a/utilities/ovs-ctl.8 +++ b/utilities/ovs-ctl.8 @@ -179,8 +179,40 @@ suppresses that behavior. . .IP "\fB\-\-ovsdb\-server\-priority=\fIniceness\fR" .IQ "\fB\-\-ovs\-vswitchd\-priority=\fIniceness\fR" -Sets the \fBnice\fR(1) level used for \fBovsdb\-server\fR and -\fBovs\-vswitchd\fR, respectively. Both default to \fB\-10\fR. +.IQ "\fB\-\-ovs\-brcompatd\-priority=\fIniceness\fR" +Sets the \fBnice\fR(1) level used for each daemon. All of them +default to \fB\-10\fR. +. +.IP "\fB\-\-ovsdb\-server\-wrapper=\fIwrapper\fR" +.IQ "\fB\-\-ovs\-vswitchd\-wrapper=\fIwrapper\fR" +.IQ "\fB\-\-ovs\-brcompatd\-wrapper=\fIwrapper\fR" +. +Configures the specified daemon to run under \fIwrapper\fR, which is +one of the following: +. +.RS +.IP "\fBvalgrind\fR" +Run the daemon under \fBvalgrind\fR(1), if it is installed, logging to +\fIdaemon\fB.valgrind.log.\fIpid\fR in the log directory. +. +.IP "\fBstrace\fR" +Run the daemon under \fBstrace\fR(1), if it is installed, logging to +\fIdaemon\fB.strace.log.\fIpid\fR in the log directory. +. +.IP "\fBglibc\fR" +Enable GNU C library features designed to find memory errors. +.RE +. +.IP +By default, no wrapper is used. +. +.IP +Each of the wrappers can expose bugs in Open vSwitch that lead to +incorrect operation, including crashes. The \fBvalgring\fR and +\fBstrace\fR wrappers greatly slow daemon operations so they should +not be used in production. They also produce voluminous logs that can +quickly fill small disk partitions. The \fBglibc\fR wrapper is less +resource-intensive but still somewhat slows the daemons. . .PP The following options control file locations. They should only be @@ -197,6 +229,12 @@ Overrides the file name for the Unix domain socket used to connect to .IP "\fB\-\-db\-schema=\fIschema\fR" Overrides the file name for the OVS database schema. . +.IP "\fB\-\-extra-dbs=\fIfile\fR" +Adds \fIfile\fR as an extra database for \fBovsdb\-server\fR to serve +out. Multiple space-separated file names may also be specified. +\fIfile\fR should begin with \fB/\fR; if it does not, then it will be +taken as relative to \fIdbdir\fR. +. .SH "The ``stop'' command" . .PP @@ -212,6 +250,14 @@ modules. This command does nothing and finishes successfully if the OVS daemons aren't running. . +.SH "The ``restart'' command" +. +.PP +The \fBrestart\fR command performs a \fBstop\fR followed by a \fBstart\fR +command. The command can take the same options as that of the \fBstart\fR +command. In addition, it saves and restores Openflow flows for each +individual bridge. +. .SH "The ``status'' command" . .PP @@ -241,31 +287,39 @@ implemented by Open vSwitch. The most common examples of these are bridge ``local ports''. . .IP 2. +Saves the Openflow flows of each bridge. +. +.IP 3. Stops the Open vSwitch daemons, as if by a call to \fBovs\-ctl stop\fR. . -.IP 3. +.IP 4. Saves the kernel configuration state of the OVS internal interfaces listed in step 1, including IP and IPv6 addresses and routing table entries. . -.IP 4. +.IP 5. Unloads the Open vSwitch kernel module (including the bridge compatibility module if it is loaded). . -.IP 5. +.IP 6. Starts OVS back up, as if by a call to \fBovs\-ctl start\fR. This -reloads the kernel module and restarts the OVS daemons (including -\fBovs\-brcompatd\fR, if \fB\-\-brcompat\fR is specified). +reloads the kernel module, restarts the OVS daemons (including +\fBovs\-brcompatd\fR, if \fB\-\-brcompat\fR is specified) and finally +restores the saved Openflow flows. . -.IP 6. -Restores the kernel configuration state that was saved in step 3. +.IP 7. +Restores the kernel configuration state that was saved in step 4. . -.PP -The steps above are often enough to hot-upgrade a new kernel module -with only a few seconds of downtime. DHCP is a common problem: if the -ISC DHCP client is running on an OVS internal interface, then it will -have to be restarted after completing the above procedure. +.IP 8. +Checks for daemons that may need to be restarted because they have +packet sockets that are listening on old instances of Open vSwitch +kernel interfaces and, if it finds any, prints a warning on stdout. +DHCP is a common example: if the ISC DHCP client is running on an OVS +internal interface, then it will have to be restarted after completing +the above procedure. (It would be nice if \fBovs\-ctl\fR could restart +daemons automatically, but the details are far too specific to a +particular distribution and installation.) . .PP \fBforce\-kmod\-reload\fR internally stops and starts OVS, so it @@ -365,6 +419,7 @@ that it runs. \fBovs\-ctl\fR will add the \fIsbindir\fR and . .IP "\fBOVS_LOGDIR\fR" .IQ "\fBOVS_RUNDIR\fR" +.IQ "\fBOVS_DBDIR\fR" .IQ "\fBOVS_SYSCONFDIR\fR" .IQ "\fBOVS_PKGDATADIR\fR" .IQ "\fBOVS_BINDIR\fR" @@ -392,7 +447,7 @@ process ID. The OVS database schema used to initialize the database (use \fB\-\-db\-schema to override this location). . -.IP "\fIsysconfdir\fB/openvswitch/conf.db\fR" +.IP "\fIdbdir\fB/conf.db\fR" The OVS database (use \fB\-\-db\-file\fR to override this location). . .IP "\fIrundir\fB/openvswitch/db.sock\fR"