Sorry for the new thread, but I thought it best not to interrupt other discussions.
I have two systems. Call them SystemK and SystemM. I compare booting on the two systems.
With SystemK, the hard disk spins for a while (I go by the light indicating disk activity). Then there is what seems to be a longish period with almost no disk activity. Finally, the login screen comes up.
With SystemM, the hard disk spins for a while. Almost as soon as the disk activity stops, the login screen comes up.
I tried: systemd-analyze blame | grep -i networkman
For SystemK, I get:
25.232s NetworkManager.service 7.574s NetworkManager-wait-online.service
while, for SystemM, I get:
It seems a good guess that the NetworkManager startup time is a big part of the problem.
What’s similar about the two systems:
- Both are on the same physical computer (a Dell laptop);
- Both use an encrypted LVM. In fact, they use the same encrypted LVM, but different root volumes within that LVM. Both use the same swap volume and the same home volume in that LVM, except that SystemM mounts the home volume as “/xhome”.
What’s different about the two systems:
- SystemK runs the KDE desktop and uses KDM as login manager;
- SystemM runs the MATE desktop and uses lightdm as login manager.
It is hard to see how those differences could matter, since the delays are there before the desktops start.
Oh, yes. There is one additional difference. And maybe this is the cause.
On SystemK, I am running “autofs”. In SystemM, I have not yet gotten around to configuring “autofs” (and might not ever bother).
But if that is the difference, it makes no sense. The whole idea of using “autofs”, instead of configuring network shares in “/etc/fstab”, is supposed to be to allow lazy mounting and to avoid having system startup delayed by network issues.