On Sat, 2021-03-27 at 22:20 -0700, Alan Perry wrote:
> On 3/27/21 5:38 AM, Lennart Poettering wrote:
> > On Fr, 26.03.21 23:24, Alan Perry (al...@snowmoose.com) wrote:
> >
> > > I occasionally see a problem where systemd-analyze reports that boot
> > > did not complete and it is suggested that I u
On 3/27/21 5:38 AM, Lennart Poettering wrote:
On Fr, 26.03.21 23:24, Alan Perry (al...@snowmoose.com) wrote:
I occasionally see a problem where systemd-analyze reports that boot
did not complete and it is suggested that I use systemctl list-jobs
to find out more. That shows a .device service j
> On Mar 27, 2021, at 05:46, Lennart Poettering wrote:
>
> On Fr, 26.03.21 23:24, Alan Perry (al...@snowmoose.com) wrote:
>
>> I occasionally see a problem where systemd-analyze reports that boot
>> did not complete and it is suggested that I use systemctl list-jobs
>> to find out more. That
On Fr, 26.03.21 23:24, Alan Perry (al...@snowmoose.com) wrote:
> I occasionally see a problem where systemd-analyze reports that boot
> did not complete and it is suggested that I use systemctl list-jobs
> to find out more. That shows a .device service job and some sub-jobs
> (associated with udev
I occasionally see a problem where systemd-analyze reports that boot did not
complete and it is suggested that I use systemctl list-jobs to find out more.
That shows a .device service job and some sub-jobs (associated with udev rules)
all waiting. They will wait for literal days in this state. W
