On 4/9/19 1:09 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Tue, Apr 09, 2019 at 06:07:09PM +0200, Lennart Poettering wrote:
> multipathd [...] And beyond that, this daemon is really ugly too: it logs
> at high log levels during boot that it found no configuration and
> hence nothing to do. Yes, obviously, but that's a reason to shut up
> and proceed quickly, not to complain loudly about that so that it
> even appears on the scren (I mean srsly, this is the first thing I
> saw when i booted from the fedora live media: a log message printed
> all over the screen that multipathd has no working
This was supposed to be fixed https://bugzilla.redhat.com/show_bug.cgi?id=1631772
If not, please reopen that bug.
> 5. libvirtd. Why is this running? Can't we make this socket
> activatable + exit-on-idel?
This was supposed to happen. See
This bug (briefly) describes why at present libvirt can't use socket
Libvirtd has a feature to autostart VMs and other resources at host boot
up, which is useful and used often that people get mad when it breaks.
We need some new work to make this play with socket activation, maybe
move the autostart checking to some separate service that runs once at
startup. But with a simple implementation Workstation wouldn't benefit
because the installed 'default' network is still set to autostart.