Bob,
Same:
# systemd-analyze critical-chain
Bootup is not yet finished. Please try again later.
The time after the unit is active or started is printed after the "@"
character.
The time the unit takes to start is printed after the "+" character.
-Mike
On Thu, Oct 27,
nactive units, too.
># systemctl is-system-running
>Unknown operation 'is-system-running'.
>
>With the systemctl status output sent to a file, I found a service
>'waiting'. I stopped it, but still get:
>
># systemd-analyze time
>Bootup is not yet fin
. I stopped it, but still get:
# systemd-analyze time
Bootup is not yet finished. Please try again later.
I don't really need the output of 'systemd-analyze time' that badly. This
was more of a curiosity.
-Mike
On Thu, Oct 27, 2016 at 12:13 PM, Dimitri John Ledkov
wrote:
>
On 27 October 2016 at 15:32, Michael MacIsaac wrote:
> I heard about this new cool command and tried it, but it did not work:
>
> # systemd-analyze time
> Bootup is not yet finished. Please try again later.
>
> How would I analyze systemd to know why 'bootup is not yet fi
>>> On 10/27/2016 at 10:32 AM, Michael MacIsaac wrote:
> How would I analyze systemd to know why 'bootup is not yet finished'? This
> is SLES 12 SP1.
It looks like systemd-analyze opens a socket to systemd and a bunch of "stuff"
gets sent back and forth
Hi Mike
I just tried that same command and it worked.
Sent from my iPhone
> On Oct 27, 2016, at 10:32 AM, Michael MacIsaac wrote:
>
> I heard about this new cool command and tried it, but it did not work:
>
> # systemd-analyze time
> Bootup is not yet finished. Plea
I heard about this new cool command and tried it, but it did not work:
# systemd-analyze time
Bootup is not yet finished. Please try again later.
How would I analyze systemd to know why 'bootup is not yet finished'? This
is SLES 12 SP1.
Thanks.
-Mik
