FS#41511 - [man-db] 2.6.7.1-1 man-db.service takes years to finish on boot
Attached to Project:
Arch Linux
Opened by Kevin Zhao (Jesse2004) - Saturday, 09 August 2014, 02:35 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 11 October 2014, 18:23 GMT
Opened by Kevin Zhao (Jesse2004) - Saturday, 09 August 2014, 02:35 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 11 October 2014, 18:23 GMT
|
Details
Description:
On the first boot of every day, when man-db.service is trigerred by man-db.timer, it takes minutes for my system to boot. Systemd-analyze shows that man-db.service is the one to be blamed. Additional info: * package version(s) man-db 2.6.7.1-1 * config and/or log files etc. $ systemd-analyze blame 1min 43.597s man-db.service 14.684s wicd.service 12.433s libvirtd.service 11.401s systemd-fsck-root.service 2.079s lvm2-pvscan@254:0.service 1.862s udisks2.service 1.844s systemd-vconsole-setup.service 1.499s systemd-modules-load.service 1.155s systemd-logind.service 1.152s systemd-nspawn@default-chroot.service 1.107s dev-mapper-FTD\x2dswap.swap 855ms polkit.service ........ Steps to reproduce: Just boot up. 
system-log
(137.3 KiB)
|
This task depends upon
Closed by Andreas Radke (AndyRTR)
Saturday, 11 October 2014, 18:23 GMT
Reason for closing: No response
Saturday, 11 October 2014, 18:23 GMT
Reason for closing: No response
8.870s updatedb.service
7.241s man-db.service
2.772s netctl@ethernet\x2dstatic.service
887ms x2goserver.service
It's also the longest taking service for me but it doesn't hang there at boot. Check the .service file. It depends on /var/cache being mounted. Nothing else. It will run in the background anyway.
I guess something else holds your boot. Check you systemd bootup maybe in graphical view mode.