Find Slow Boot Services with systemd-analyze blame
systemd-analyze blame ranks every unit by the time it took to initialize, revealing what delays startup.
01Command
$ systemd-analyze blame02What it does
Plain `systemd-analyze` prints overall figures like "Startup finished in 2.1s (kernel) + 8.4s (userspace)", while blame breaks the userspace part down per unit. Note the times measure each unit's own initialization, not waiting for dependencies — use `systemd-analyze critical-chain` for that view. A high blame entry usually means the service can be disabled, masked, or configured differently.
03Risk
04Undo
✓No undo needed — this command does not change persistent state.
05Sources
- systemd-analyze(1)Evidence: blame prints a list of all currently running units, ordered by the time they took to initialize.
Last verified: 2026-09-17 · Category: System & Settings
06Related solutions
timedatectl lists, sets, and verifies the system timezone and NTP sync status on systemd distributions.
hostnamectl sets the static, transient, and pretty hostname in one step on systemd distros, no reboot required.
systemctl list-timers shows every scheduled timer unit with its last and next run times, which many users forget replaces cron on modern distros.