You are not logged in.
Pages: 1
I can not disable man-db service.
[burak@thinkpad] <~> ➤ systemd-analyze blame
5.176s man-db.service
1.305s systemd-random-seed.service
285ms dev-nvme0n1p3.device
236ms udisks2.service
104ms boot.mount
81ms user@1000.service
71ms systemd-rfkill.service
52ms polkit.service
49ms upower.service
47ms systemd-udev-trigger.service
37ms NetworkManager.service
37ms systemd-modules-load.service
36ms lvm2-monitor.service
36ms systemd-timesyncd.service
35ms systemd-tmpfiles-setup-dev.service
34ms packagekit.service
34ms systemd-udevd.service
33ms systemd-logind.service
28ms systemd-journald.service
28ms systemd-fsck@dev-disk-by\x2duuid-FEB4\x2dE2FA.service
25ms systemd-tmpfiles-setup.service
15ms modprobe@drm.service
11ms systemd-binfmt.service
10ms dev-hugepages.mount
9ms dev-mqueue.mount
9ms wpa_supplicant.service
9ms bluetooth.service
9ms sys-kernel-debug.mount
8ms dev-disk-by\x2duuid-1591aecb\x2d316d\x2d4113\x2dbd90\x2ddf62460f39e5.swap
8ms sys-kernel-tracing.mount
8ms kmod-static-nodes.service
7ms modprobe@fuse.service
7ms systemd-backlight@backlight:amdgpu_bl0.service
7ms modprobe@configfs.service
6ms systemd-update-utmp.service
5ms systemd-remount-fs.service
5ms user-runtime-dir@1000.service
5ms systemd-journal-flush.service
4ms sys-fs-fuse-connections.mount
4ms systemd-user-sessions.service
4ms systemd-sysctl.service
3ms alsa-restore.service
3ms rtkit-daemon.service
2ms proc-sys-fs-binfmt_misc.mount
2ms sys-kernel-config.mount
1ms tmp.mountThat service adds huge time to boot sequence, so I am disabling it. However, somehow it is enabling itself again for unknown reason, what can I do about it ?
Offline
You could mask it. Or, you could find out why it is taking so long. Or, you could read the note here and reschedule it: https://wiki.archlinux.org/title/System … time_timer
Offline
Pages: 1