[Sorry in advance for the formatting, submitting on mobile. Raw patch
attached.]
As handling software via cgroups is more and more common, PID files are
not always needed. This change adds --disable-pid-socket-path to
./configure to build OpenvSwitch without this PID section of the socket
path. This offers a way for software to easier know the socket path for
daemons independent on which platform it is running on.
Today the socket path is by default one of:
Linux: RUNDIR/daemon.$PID.ctl
Windows: RUNDIR/daemon.ctl
For Linux it is thus commonplace to also run the daemon with --pidfile
to be able to communicate with the daemon. For Windows there is no such
need (or possibility).
In order to preserve default behavior the new flag ships as enabled.
Documentation currently describes the default behavior only.
ovsdb-client is updated to support setting explicit socket path when
running in detached mode.
This closes https://github.com/openvswitch/ovs-issues/issues/114.
Signed-off-by: Christian Svensson <blue...@google.com>
---
AUTHORS | 1 +
Makefile.am | 4 ++++
configure.ac | 1 +
lib/unixctl.c | 4 +++-
m4/openvswitch.m4 | 22 ++++++++++++++++++++++
ovsdb/ovsdb-client.c | 13 +++++++++++--
python/automake.mk | 6 ++++--
python/ovs/dirs.py | 2 ++
python/ovs/dirs.py.template | 2 ++
python/ovs/unixctl/__init__.py | 3 +++
python/ovs/unixctl/server.py | 4 +++-
tests/atlocal.in | 1 +
tests/ovn-controller-vtep.at | 4 ++--
tests/ovsdb-lock.at | 2 +-
tests/ovsdb-monitor.at | 7 +++----
tests/unixctl-py.at | 10 +++++-----
utilities/ovs-appctl.c | 9 ++++++---
17 files changed, 74 insertions(+), 21 deletions(-)
https://github.com/bluecmd/ovs/commit/71a2775c58bbf77d2eb2351f3493ef60143f6dcd.patch
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
