From: robin_listas@es.invalid   
      
   On 2022-04-17 09:16, Andrew wrote:   
   > Carlos E.R. wrote:   
   >> On 2022-04-14 13:11, Tristan Miller wrote:   
   >>> Greetings.   
   >>>   
   >>> Occasionally when I boot my machine, the system pauses for a minute   
   >>> or two with the message, "A start job is running for Purge old kernels".   
   >>>   
   >>> If I understand correctly, purging old kernels simply means   
   >>> uninstalling them.  If this is the case, why is this something that   
   >>> boot has to block for?  I mean, once the system is up an running, I   
   >>> can always use zypper or rpm to manually remove old kernels.  So it's   
   >>> obviously something that *can* be done without interfering with my   
   >>> use of the machine.  I get why the bootup script might want to clean   
   >>> up old kernels every once in a while, but why can't it just launch a   
   >>> process that does this unobtrusively in the background?   
   >>   
   >> AFAIK, it doesn't block here, other things continue running, even the   
   >> boot sequence. I can not check this instant, but I think I can login   
   >> while the job is running. I should be able to verify this tomorrow.   
   >>   
   >> You do not say what release you are using.   
   >>   
   >>   
   >> The job simply calls on zypper to delete the oldest kernel after an   
   >> update.   
   >>   
   >> You can verify what it does by running:   
   >>   
   >> systemctl cat purge-kernels.service   
   >>   
   >>   
   > I have Leap 15.3 with the splash screen turned off so that I can see   
   > what is going on.  The script runs as part of the boot process and   
   > *before* logging in is possible, this is obviously what Tristan sees as   
   > well.  In my case - on my old laptop, no ssd - it delays the appearance   
   > of the login screen by just over a minute.   
   > No idea if this is something new, I'll often boot and then get on with   
   > something else for a minute or two.  It *is* something I first noticed a   
   > couple of days before Tristan reported it here.   
   >   
      
   I booted this Leap 15.3 today after a kernel update. I did:   
      
   systemd-analyze plot >bootup.svg   
   eog bootup.svg   
      
      
   And I clearly see that the boot process continues running while   
   purge-kernels is running (for 41 seconds in my case).   
      
   It is the service "display-manager" which waits, apparently.   
      
      
   You can run "systemd-analyze critical-chain", but in my case   
   "purge-kernels" is not listed, which I think it means it does not delay   
   others.   
      
      
   I suggest you ask in the support mail list.   
      
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)