You are not logged in.
With the latest update of man-db in [testing], there seems to be a new systemd service (file); when I checked the systemd startup time, it seemed awfully long - more than 17 seconds(!); why so?
systemd-analyze blame | grep man-db
17.366s man-db.service
Last edited by rainbowdashc (2014-04-14 16:02:28)
Offline
It is triggered by a systemd.timer. These have been put in use in place of anacron. So if your comptuer was due for this to be run while the machine was off, it does it upon restart/wake/whatever. This is not something that will happen frequently.
Check out the timer unit to see how frequently it runs. It is really no different than the time intervals that were in place before with anacron.
Offline
Edit: restarted and back to normal.
Offline
systemd-analyze blame is not just about starting your system - it collect info about what has been run since you're rebooted. If you run it right after boot, it shouws info about startup, but then it adds other info, like man-db.service etc.
Offline