On Wed, Jun 21, 2023 at 14:32:30 +0100, Daniel P. Berrangé wrote:
> Historically we wanted to check if logind was actually running, not
> merely activatable, because on systems where systemd is installed,
> but the OS is booted into non-systemd init, we want to fallback to
> pm-utils.
>
> Requirin
On Thu, Jun 22, 2023 at 09:49:41AM +0100, Daniel P. Berrangé wrote:
> On Thu, Jun 22, 2023 at 10:23:57AM +0200, Peter Krempa wrote:
> > On Wed, Jun 21, 2023 at 14:32:30 +0100, Daniel P. Berrangé wrote:
> > > +/*
> > > + * Want to use logind if:
> > > + * - logind is already running
>
On Thu, Jun 22, 2023 at 10:23:57AM +0200, Peter Krempa wrote:
> On Wed, Jun 21, 2023 at 14:32:30 +0100, Daniel P. Berrangé wrote:
> > Historically we wanted to check if logind was actually running, not
> > merely activatable, because on systems where systemd is installed,
> > but the OS is booted i
On Wed, Jun 21, 2023 at 14:32:30 +0100, Daniel P. Berrangé wrote:
> Historically we wanted to check if logind was actually running, not
> merely activatable, because on systems where systemd is installed,
> but the OS is booted into non-systemd init, we want to fallback to
> pm-utils.
>
> Requirin
Historically we wanted to check if logind was actually running, not
merely activatable, because on systems where systemd is installed,
but the OS is booted into non-systemd init, we want to fallback to
pm-utils.
Requiring logind to be running, however, forces us to serialize libvirtd
startup on st
