Re: [PATCH 2/2] Report better error message in remoteGetUNIXSocket

On Wed, Nov 29, 2023 at 05:44:59AM -0500, Andrea Bolognani wrote: > On Wed, Nov 29, 2023 at 10:09:36AM +0000, Richard W.M. Jones wrote: > > Why is it exactly that the socket doesn't work after installation, but > > does work after reboot? On my laptop, the socket unit is set to > > "disabled", yet libvirt works fine (since the laptop has been rebooted > > since libvirt was installed, I guess). Shouldn't the command be > > "systemctl enable virtqemud.socket --now"? > > It's a distro policy. > > I assume you're running Fedora/RHEL on your laptop, and the policy > there is that services (or sockets) should not be started right after > a package is installed. Debian has the opposite policy. I think this is a very weird choice (for Fedora). Why would installing the package not start the service, but then the service would be started without further intervention after reboot? It's the opposite of predictable behaviour.