Mein Systemstart wird durch updatedb.service und man-db.service ziemlich verzögert:
$ systemd-analyze blame
41.288s updatedb.service
18.518s man-db.service
13.380s mysqld.service
9.513s httpd.service
8.233s smbd.service
6.411s lvm2-pvscan@254:0.service
5.391s shadow.service
4.678s lm_sensors.service
3.714s alsa-restore.service
3.699s rpcbind.service
3.698s systemd-user-sessions.service
3.698s dhcpcd.service
3.697s avahi-daemon.service
2.143s colord.service
1.993s systemd-journal-flush.service
1.740s lvm2-pvscan@8:20.service
1.667s systemd-fsck-root.service
1.650s systemd-cryptsetup@Daten.service
1.636s systemd-cryptsetup@backup.service
1.488s logrotate.service
1.473s mnt-Medien.mount
1.370s systemd-modules-load.service
1.101s systemd-logind.service
1.037s systemd-vconsole-setup.service
1.016s systemd-fsck@dev-disk-by\x2duuid-6a7654fa\x2d0437\x2d4615\x2d9cf0\x2d7b315129dfe0.service
797ms systemd-udevd.service
770ms sys-kernel-debug.mount
753ms dev-hugepages.mount
684ms udisks2.service
657ms systemd-journald.service
505ms sys-fs-fuse-connections.mount
503ms dev-mqueue.mount
478ms tmp.mount
473ms ntpd.service
447ms dev-disk-by\x2duuid-d9e9d59b\x2d8e38\x2d48d0\x2d87da\x2d725e8e503167.swap
382ms systemd-fsck@dev-disk-by\x2duuid-53e6235f\x2def63\x2d4ebd\x2d8aee\x2d5fb788c860fb.service
351ms systemd-fsck@dev-mapper-backup.service
351ms systemd-tmpfiles-setup-dev.service
326ms kmod-static-nodes.service
298ms systemd-sysctl.service
268ms systemd-udev-trigger.service
255ms systemd-fsck@dev-mapper-Daten.service
254ms home.mount
252ms polkit.service
234ms rtkit-daemon.service
228ms systemd-tmpfiles-setup.service
193ms systemd-update-utmp.service
106ms mnt-Daten.mount
Der Versuch, in den jeweiligen Dateien
/var/lib/systemd/timers/stamp-updatedb.timer
/var/lib/systemd/timers/stamp-man-db.timer
/var/lib/systemd/system/updatedb.service
/usr/lib/systemd/system/man-db.service
den Start der beiden Services mit
[Timer]
OnBootSec=90min
zu verschieben funktioniert - siehe oben - nicht. Hab ich da nen (Denk-)Fehler drin?