summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Pfaff <blp@nicira.com>2010-06-18 15:58:13 -0700
committerBen Pfaff <blp@nicira.com>2010-06-23 09:54:14 -0700
commitcb8141b2334a54d45bddefda3bf537f2907eec7b (patch)
treeb318830d91fdfdb75ba12824ebc4fc859d7153cb
parent254604d84b48fde8e19299a10be7145adee52f98 (diff)
downloadopenvswitch-cb8141b2334a54d45bddefda3bf537f2907eec7b.tar.gz
Better document how ovsdb-server is meant to be used.
DarkBls <darkbls@yahoo.com> had the idea that a single ovsdb-server could be used to serve configuration details across the network to multiple remote ovs-vswitchd instances. This doesn't work, but the documentation didn't spell it out. This commit should help.
-rw-r--r--INSTALL.Linux7
-rw-r--r--vswitchd/ovs-vswitchd.8.in7
2 files changed, 8 insertions, 6 deletions
diff --git a/INSTALL.Linux b/INSTALL.Linux
index bd7038c85..b4f9b7678 100644
--- a/INSTALL.Linux
+++ b/INSTALL.Linux
@@ -229,9 +229,10 @@ Startup
=======
Before starting ovs-vswitchd itself, you need to start its
-configuration database, ovsdb-server. Configure it to use the
-database you created during step 7 of installation, above, and to
-listen on a Unix domain socket, e.g.:
+configuration database, ovsdb-server. Each machine on which Open
+vSwitch is installed should run its own copy of ovsdb-server.
+Configure it to use the database you created during step 7 of
+installation, above, and to listen on a Unix domain socket, e.g.:
% ovsdb-server /usr/local/etc/ovs-vswitchd.conf.db --remote=punix:/usr/local/var/run/openvswitch/db.sock
diff --git a/vswitchd/ovs-vswitchd.8.in b/vswitchd/ovs-vswitchd.8.in
index 0a7369e90..0e5d3188e 100644
--- a/vswitchd/ovs-vswitchd.8.in
+++ b/vswitchd/ovs-vswitchd.8.in
@@ -18,9 +18,10 @@ ovs\-vswitchd \- Open vSwitch daemon
A daemon that manages and controls any number of Open vSwitch switches
on the local machine.
.PP
-The mandatory \fIdatabase\fR argument specifies the
-\fBovsdb\-server\fR from which \fBovs\-vswitchd\fR's configuration
-should be retrieved. It takes one of the following forms:
+The mandatory \fIdatabase\fR argument normally takes the form
+\fBunix:\fIfile\fR, where \fIfile\fR is the name of a Unix domain
+socket on which \fBovsdb-server\fR is listening. However, all of the
+following forms are accepted:
.so ovsdb/remote-active.man
.so ovsdb/remote-passive.man
.PP