On Fri, Jul 18, 2014 at 12:28 AM, Luis R. Rodriguez <mcg...@do-not-panic.com> wrote: > From: "Luis R. Rodriguez" <mcg...@suse.com> > > This adds systemd socket activation support for the C xenstored. > Active sockets enable xenstored to be loaded only if required by a system > onto which Xen is installed on. Socket activation is handled by > systemd, once a port for a service which claims a socket is used > systemd will start the required services for it, on demand. For more > details on socket activation refer to Lennart's socket-activation > post regarding this [0]. > > Right now this code adds a no-op for this functionality, leaving the > enablement to be done later once systemd is properly hooked into > the build system. The socket activation is ordered in aligment with > the socket activation order passed on to systemd. > > [0] http://0pointer.de/blog/projects/socket-activation2.html
So with this patch in place, xenstored will not start on a system that has systemd, *even if it wasn't started from systemd*. Lots of systems (e.g., CentOS 7) have legacy systems in place to allow you to do things like "chkconfig --add xencommons" even on a systemd system. I think we still want to work with those, right? -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
