Bug 963525
| Summary: | abrtd modifies old directories | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> |
| Component: | abrt | Assignee: | Jakub Filak <jfilak> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | abrt-devel-list, dvlasenk, iprikryl, jberan, jfilak, maurizio.antillon, mmilata, rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| URL: | https://github.com/abrt/abrt/issues/1162 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-19 10:12:25 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
John Reiser
2013-05-16 04:15:59 UTC
abrtd changes the modification timestamp for several reasons and it is not possible to get rid of them. The first reason is that a dump directory is used as a communication channel. The principle is simple, one tool creates a file inside the directory and an another one processes the file. And the synchronization algorithm is based on creating ".lock" symbolic links inside a dump directory. A tool creates the ".lock" link inside a directory to prevent other tools from modification of the directory. If one tools finds the ".lock" link inside a directory, it waits until the link is removed and then continues in processing. I would say 'abrt-cli list' could help you but I am afraid that 'abrt-cli list' misses some arguments you need. We can add more arguments there but we are not sure which. It seems to me that it ought to be possible to avoid changing the modification timestamp on an old dump directory. Look first for a .lock file; if found, then skip to next directory, or wait as now. If no .lock file, then look if any action is necessary, without setting a .lock file yet. If no action is necessary, then skip to next directory, and changing the modification timestamp has been avoided. If action appears to be necessary, or if not enough files are present to determine whether action is necessary, then establish the .lock file and proceed as now. Overall, in one common case (a dump directory which was completely processed at least many minutes ago) setting the .lock can be avoided, thus not changing the modification timestamp. (In reply to comment #2) Yes, your idea is correct. But all I can promise is that I will look into it but it won't be implemented soon. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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. This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. Moved upstream: https://github.com/abrt/abrt/issues/1162 |