On Fri, 2019-07-26 at 16:22 +0100, Daniel P. Berrangé wrote:
> On Fri, Jul 26, 2019 at 03:59:23PM +0200, Andrea Bolognani wrote:
> > On Tue, 2019-07-23 at 17:02 +0100, Daniel P. Berrangé wrote:
> > > +remote/libvirtd.conf: remote/libvirtd.conf.in
> > > + $(AM_V_GEN)sed \
> > > + -e '/:: CUT
On Fri, Jul 26, 2019 at 03:59:23PM +0200, Andrea Bolognani wrote:
> On Tue, 2019-07-23 at 17:02 +0100, Daniel P. Berrangé wrote:
> > +remote/libvirtd.conf: remote/libvirtd.conf.in
> > + $(AM_V_GEN)sed \
> > + -e '/:: CUT ENABLE_IP ::/d' \
> > + -e '/:: END ::/d' \
> > +
On Tue, 2019-07-23 at 17:02 +0100, Daniel P. Berrangé wrote:
> +remote/libvirtd.conf: remote/libvirtd.conf.in
> + $(AM_V_GEN)sed \
> + -e '/:: CUT ENABLE_IP ::/d' \
> + -e '/:: END ::/d' \
> + -e 's/:: DAEMON_NAME ::/libvirtd/' \
> + < $^ > $@
Us
Prepare for reusing libvirtd config to create other daemons by making
the config parameters for IP sockets conditionally defined by the make
rules.
The main libvirtd daemon will retain IP listen ability, but all the
driver specific daemons will be local UNIX sockets only. Apps needing
IP connectiv
