On Fri, 25 Aug 2017 07:42:00 +0200 Rico Heil <[email protected]> wrote:
>> 3. run: systemd-analyze blame >Didn't know that command, but it does look really interesting - >thanks for showing it to me :-) > > >> I wouldn't be surprised if you had the updatedb and the >> updatedb.timer process running. >I don't see any updatedb processes in the list, but the top time >consumer is man-db.service now with over 17 seconds - maybe this was >the culprit. The only thing I don't understand is, why this number >should be relevant for my problem. > > From "systemd-analyze --help": >blame Print list of running units ordered by time to init > >Why is time to init relevant here? Many of these services are running in the background and much of man-db and updatedb are disk IO which "kills everything else". Alternatively use htop to see what's hogging the CPU and/or the IO while in DT -- sknahT vyS ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
