INSTALL.Windows: Correct invalid paths.

commit 0be55e389d2f1 (INSTALL.Windows: Add documentation about Windows
services.) added documentation about starting Windows services but
provided wrong executable paths. This commit fixes it.

Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
Acked-by: Nithin Raju <nithin@vmware.com>

diff --git a/INSTALL.Windows.md b/INSTALL.Windows.md
index 00db4a3..0029500 100644 (file)
--- a/INSTALL.Windows.md
+++ b/INSTALL.Windows.md
@@ -430,7 +430,7 @@ MSYS bash or Windows command prompt.
 
 * Create the ovsdb-server service and start it.
 
-  % sc create ovsdb-server binpath="C:/Shares/openvswitch/ovsdb/ovsdb-server.exe C:/openvswitch/etc/openvswitch/conf.db -vfile:info --log-file --pidfile --remote=punix:db.sock --service --service-monitor"
+  % sc create ovsdb-server binpath="C:/openvswitch/usr/sbin/ovsdb-server.exe C:/openvswitch/etc/openvswitch/conf.db -vfile:info --log-file --pidfile --remote=punix:db.sock --service --service-monitor"
 
   One of the common issues with creating a Windows service is with mungled
   paths. You can make sure that the correct path has been registered with
@@ -452,7 +452,7 @@ MSYS bash or Windows command prompt.
 
 * Create the ovs-vswitchd service and start it.
 
-  % sc create ovs-vswitchd binpath="C:/Shares/openvswitch/vswitchd/ovs-vswitchd.exe --pidfile -vfile:info --log-file  --service --service-monitor"
+  % sc create ovs-vswitchd binpath="C:/openvswitch/usr/sbin/ovs-vswitchd.exe --pidfile -vfile:info --log-file  --service --service-monitor"
 
   % sc start ovs-vswitchd