Bug 1678464
| Summary: | Consider moving man-db-cache-update to after boot instead of at shutdown | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kevin Fenzi <kevin> |
| Component: | man-db | Assignee: | Nikola Forró <nforro> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 32 | CC: | jchaloup, me, nforro, prd-fedora, stijn, yaneti |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | man-db-2.8.7-2.fc32 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-25 15:00:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kevin Fenzi
2019-02-18 20:44:35 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. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. 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. 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. 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? Good point, it does block multi-user.target, which is most likely not what we want. I've updated the PR. 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. This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. Would love to see this backported to all supported versions. Please. 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. 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed. |