Bug 1678464 - Consider moving man-db-cache-update to after boot instead of at shutdown
Summary: Consider moving man-db-cache-update to after boot instead of at shutdown
Alias: None
Product: Fedora
Classification: Fedora
Component: man-db
Version: 32
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Nikola Forró
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2019-02-18 20:44 UTC by Kevin Fenzi
Modified: 2021-05-25 15:00 UTC (History)
6 users (show)

Fixed In Version: man-db-2.8.7-2.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-05-25 15:00:06 UTC
Type: Bug

Attachments (Terms of Use)

Description Kevin Fenzi 2019-02-18 20:44:35 UTC
Last week my main server/gateway lost a interface (probibly a hardware bug), so I went to quickly reboot it. Imagine my dismay as I saw the reboot process stall for 3 minutes (out of "no limit") running man-db cache refresh. I couldn't stop it or do anything, I just had to wait. 

Please consider moving this job to something like '30min after boot' or the like where it can run in the background and not bother people when they need a quick reboot.

Comment 1 Brian Lane 2019-07-31 17:54:39 UTC
I just hit this as well, on a F30 system using man-db-2.8.4-4.fc30.x86_64
It now has a 15min timeout but that still doesn't help when you are trying to quickly reboot.

Comment 2 Ben Cotton 2019-08-13 18:51:39 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Stijn Hoop 2019-09-20 10:02:38 UTC
Hitting this as well on both F30 and F31 beta just after upgrade. Is very annoying to wait at least a few minutes when you're rebooting after installing updates.

Comment 4 Nikola Forró 2019-09-27 11:47:10 UTC
Sorry it took me so long. I've come up with the following solution: https://src.fedoraproject.org/rpms/man-db/pull-request/6#request_diff

Enabling and disabling the service by itself in the unit file seems a bit hackish, but I couldn't think of anything better.

Comment 5 Kevin Fenzi 2019-09-27 14:26:04 UTC
So just to be clear, that runs on boot, but doesn't block bootup? Or does the boot block waiting for that to complete before the machine is fully up?

Comment 6 Nikola Forró 2019-09-27 15:32:00 UTC
Good point, it does block multi-user.target, which is most likely not what we want. I've updated the PR.

Comment 7 Nikola Forró 2019-10-10 12:52:56 UTC
Pushed and built in rawhide: https://src.fedoraproject.org/rpms/man-db/c/75b683fe495e761059857c797159610881208ca6?branch=master

I decided not to deploy this into stable releases, I'd rather get some feedback first.

Comment 8 Ben Cotton 2020-02-11 15:41:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 9 Mike Ely 2020-05-08 19:20:57 UTC
Would love to see this backported to all supported versions. Please.

Comment 10 Fedora Program Management 2021-04-29 15:55:15 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Ben Cotton 2021-05-25 15:00:06 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.