On Mon, Aug 08, 2016 at 10:49:21AM +0200, Christian Svensson wrote: > 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>
I don't think it's reasonable to make this a configuration-time option. I want Open vSwitch behavior to be fairly uniform at runtime, not unpredictable based on whatever flags were supplied at build time. I suggest that you just use "--pidfile=<program>.pid" on the command line, instead. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
