On Thu, Apr 13, 2017 at 01:51:29PM -0400, Aaron Conole wrote: > The install documentation guided users to manually start/stop > daemons. This is good information to have, but with the > existence of ovs-ctl, is probably not the best way to start > guiding new users of ovs. > > Suggest that users start by running ovs-ctl start, and > document the ability to selectively start/stop the daemons. > The ovs-ctl script is already mentioned a bit in the install > doc, so this just reinforces its use. > > Suggested-by: Ben Pfaff <[email protected]> > Signed-off-by: Aaron Conole <[email protected]>
Thanks for working on the documentation! I am a little worried about adding the casual suggestion to call ovs-ctl, because ovs-ctl is installed in an out-of-the-way scripts directory that is not in $PATH by default. This is because ovs-ctl is mostly meant as a tool for use by system init scripts rather than one for the system administrator. So, if we suggest that the admin should call it directly, then we should either advise the admin where to find it, or we should consider moving it to the default $PATH. What do you think is the best idea? _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
