From: SKRdJ@nowhere.net   
      
   On Mon, 6 Jun 2022 17:57:15 -0000 (UTC), Henrik Carlqvist wrote:   
      
   > Even if you killed the terminal, your ls process is probably still there   
   > in a "D" state (waiting for disk) and your system load is the sum of all   
   > processes wayting for CPU and all processes waiting for disk.   
      
   	Thanks. That did the trick: I had three processes in a "D" state   
   (actually, D and something else) - one of them being indeed the shell   
   where I tried to do the ls. After killing them the system load is back to   
   the levels that I would expect from the ordinary system activity.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)