FS#70132 - [man-db] timer daily is activated and slows a lot boot process.

Attached to Project: Arch Linux
Opened by Frederic Bezies (fredbezies) - Tuesday, 23 March 2021, 08:28 GMT
Last edited by Toolybird (Toolybird) - Monday, 03 April 2023, 20:38 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Hello.

I noticed since last systemd upgrade, man-db.timer is activated on a daily usage. I eats a lot of time.

Here is the beginning systemd-analyze blame:

systemd-analyze blame
1min 25.219s man-db.service
931ms systemd-random-seed.service


Additional info:
systemd 248rc4-1

Steps to reproduce:

Just install this version of systemd and look at man-db.timer. It will be set for a daily usage.

Adding full systemd-analyze blame log. It could help.
   blame.log (2.2 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 03 April 2023, 20:38 GMT
Reason for closing:  Fixed
Additional comments about closing:  See comments
Comment by Doug Newgard (Scimmia) - Tuesday, 23 March 2021, 17:29 GMT
It's always been set to run daily. If the system was off, it would run at boot, but shouldn't block anything.
Comment by Alexandre Bouvier (doskoi) - Saturday, 27 March 2021, 13:16 GMT
RandomizedDelaySec=1h can be added to the [Timer] section of man-db.timer to avoid slowing down the system startup.
Comment by lukpod (lukpod) - Monday, 03 April 2023, 17:01 GMT
https://gitlab.com/man-db/man-db/-/commit/a73c24f6a7b5de171286cf1d3010faad9944ddfc

Loading...