systemd-analyze blame
42.110s systemd-journal-flush.service
8.420s apparmor.service
3.710s SuSEfirewall2_init.service
3.019s ModemManager.service
2.930s dev-sda2.device
2.745s colord.service
2.441s display-manager.service
2.291s libvirtd.service
2.103s rtkit-daemon.service
2.101s postfix.service
2.035s var-lib-mysql.mount
1.774s systemd-fsck@dev-disk-by\x2duuid-161ab58c\x2d05a1\x2d48f7\x2d95
1.765s var-lib-pgsql.mount
1.764s var-lib-machines.mount
1.662s SuSEfirewall2.service
1.608s var-lib-mailman.mount
1.423s boot-grub2-i386\x2dpc.mount
1.372s home.mount
1.232s accounts-daemon.service
1.213s var-lib-mariadb.mount
1.205s var-cache.mount
1.178s var-lib-named.mount
1.172s var-opt.mount
1.152s var-lib-libvirt-images.mount
1.105s ntpd.service
1.090s systemd-udevd.service
1.046s polkit.service
869ms var-crash.mount
827ms srv.mount
814ms boot-grub2-x86_64\x2defi.mount
793ms dev-disk-by\x2duuid-0dd6df78\x2db1bb\x2d4e86\x2db1fc\x2d586bfe0
778ms systemd-journald.service
706ms plymouth-start.service
676ms var-log.mount
573ms avahi-daemon.service
557ms opt.mount
539ms rc-local.service
535ms usr-local.mount
519ms systemd-remount-fs.service
496ms dev-hugepages.mount
495ms dev-mqueue.mount
465ms plymouth-read-write.service
442ms NetworkManager.service
414ms systemd-user-sessions.service
401ms systemd-logind.service
368ms systemd-udev-root-symlink.service
367ms systemd-modules-load.service
348ms var-spool.mount
322ms nscd.service
316ms auditd.service
304ms var-tmp.mount
289ms tmp.mount
276ms dracut-shutdown.service
270ms systemd-sysctl.service
268ms systemd-tmpfiles-setup-dev.service
267ms mcelog.service
240ms systemd-vconsole-setup.service
238ms iscsi.service
237ms systemd-rfkill.service
176ms upower.service
168ms systemd-udev-trigger.service
142ms udisks2.service
141ms \x2esnapshots.mount
136ms sys-kernel-debug.mount
122ms systemd-fsck-root.service
114ms wpa_supplicant.service
101ms systemd-backlight@backlight:acpi_video0.service
87ms user@1000.service
79ms systemd-random-seed.service
58ms systemd-backlight@backlight:intel_backlight.service
47ms packagekit.service
43ms systemd-tmpfiles-setup.service
26ms systemd-update-utmp.service
13ms systemd-tmpfiles-clean.service
9ms alsa-restore.service
7ms sys-fs-fuse-connections.mount
6ms kmod-static-nodes.service
4ms systemd-update-utmp-runlevel.service
systemd-analyze critical-chain
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.
graphical.target @57.164s
└─display-manager.service @54.722s +2.441s
└─time-sync.target @54.612s
└─ntpd.service @53.506s +1.105s
└─network.target @53.469s
└─wpa_supplicant.service @56.399s +114ms
└─basic.target @48.746s
└─sockets.target @48.746s
└─virtlogd.socket @48.745s
└─sysinit.target @48.740s
└─systemd-update-utmp.service @48.713s +26ms
└─systemd-tmpfiles-setup.service @48.653s +43ms
└─systemd-journal-flush.service @6.501s +42.110s
└─var-log.mount @5.783s +676ms
└─dev-disk-by\x2duuid-a3bdf827\x2dbb1d\x2d4b02\x2d9a71
Question: are there consequences for running journalctl and systemd-analyze commands as root? Or they should be run as root anyways? Please don’t ignore this question please