On Tue, Sep 07, 2010 at 05:10:56PM +0100, Daniel P. Berrange wrote:
libvirtd has never explicitly auto-started avahi. libvirtd uses the avahi client library and gives it a callback to be invoked whenever a connection to the avahi daemon is established. With the old init system, if avahi wasn't started on boot, the callback isn't invoked and so libvirt never registers its mdns service. The sysadmin can start avahi at any time later, and libvirt will automatically register with it. With system-d it sounds like creating the avahi client will always immediately activate the avahi service. I think there perhaps needs to be a way to prevent autostart by the avahi client library
Can we get this in bugzilla? -- Matthew Miller <mattdm@mattdm.org> Senior Systems Architect -- Instructional & Research Computing Services Harvard School of Engineering & Applied Sciences