From aeef025a4a70352203852258b8fc1339a735139d Mon Sep 17 00:00:00 2001 From: Gurucharan Shetty Date: Thu, 9 Apr 2015 13:36:39 -0700 Subject: [PATCH] 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 Acked-by: Nithin Raju --- INSTALL.Windows.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/INSTALL.Windows.md b/INSTALL.Windows.md index 00db4a374..002950079 100644 --- 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 -- 2.20.1