fail_mode = cfg_get_string(0, "mgmt.fail-mode");
}
ofproto_set_failure(br->ofproto,
- fail_mode && (!strcmp(fail_mode, "standalone") ||
- !strcmp(fail_mode, "open")));
+ (!fail_mode
+ || !strcmp(fail_mode, "standalone")
+ || !strcmp(fail_mode, "open")));
probe = cfg_get_int(0, "%s.inactivity-probe", pfx);
ofproto_set_probe_interval(br->ofproto,
can pass through the switch at all.
.IP
The first of these that is set takes effect.
-If the value is \fBstandalone\fR, or if neither of these settings is
-set, \fBvswitchd\fR will take over responsibility for setting up
+If the value is \fBstandalone\fR, \fBvswitchd\fR will take over
+responsibility for setting up
flows when no message has been received from the controller for three
times the inactivity probe interval (see above). In this mode,
\fBvswitchd\fR causes the datapath to act like an ordinary
to the controller in the background and, when the connection succeeds,
it discontinues its standalone behavior.
.IP
-If this option is set to \fBsecure\fR, \fBvswitchd\fR will not set up
-flows on its own when the controller connection fails.
+If this option is set to \fBsecure\fR, or if neither of these settings
+is set, \fBvswitchd\fR will not set up flows on its own when the
+controller connection fails.
.IP "\fBbridge.\fIname\fB.controller.max-backoff=\fIsecs\fR"
Sets the maximum time between attempts to connect to the controller to
\fIsecs\fR, which must be at least 1. The actual interval between