| Summary: | Please enable mlocate-updatedb.timer in 90-default.preset policy | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Michal Sekletar <msekleta> |
| Component: | redhat-release | Assignee: | Josh Boyer <jwboyer> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | david.lee, fixing-stuff-d-f-crisman-redhat-bugzilla, fkrska, jwboyer, lisas, lnykryn, pkotvan, pzatko, redhat-bugzilla, robert.scheck |
| Target Milestone: | rc | Keywords: | TestCaseNeeded |
| Target Release: | 8.3 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
.`mlocate-updatedb.timer` is now enabled during the `mlocate` package installation
Previously, reindexing of the file database was not performed automatically, because the `mlocate-updatedb.timer` timer was disabled after the `mlocate` package installation.
With this update, the `mlocate-updatedb.timer` timer is now a part of the `90-default.preset` file and is enabled by default after the `mlocate` package installation. As a result, the file database is updated automatically.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-18 13:12:51 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: | |
|
Description
Michal Sekletar
2020-03-26 15:56:55 UTC
Cross-filed case 02811696 at the Red Hat customer portal. We are preparing to roll out RHEL8 (8.3) across the site, and we, too, encounter this problem. * Could you confirm, please, that the problem is still to be expected at 8.3. * It seems that RH's intended fix will be to add something like "enable mlocate-updatedb.timer" "to "/usr/lib/systemd/system-preset/90-default.preset". I can confirm that anything resembling that line seems absent from our file of that name. Could you confirm, please, that this current absence is to be expected. * Assuming that our current state (above) is correct, could you advise, please, on a reasonable workaround that will be in line with your proposed fix. I guess this will be something like us creating a file containing that "enable..." line somewhere under "/etc/systemd", but your confirmation (and even suggested recipe) of this would be useful, please. Thanks. -- David Lee -- Diamond Light Source Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (redhat-release bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:1569 |