+++ This bug was initially created as a clone of Bug #811733 +++ Description of problem: Currently abrt-vmcore service is enabled by default and it moves vmcore out of /var/crash into /var/spool/abrt. This is wrong for multiple reasons and needs fixing. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from jmoskovc on 2012-08-09 18:13:03 EDT --- We could use hardlinks instead of copying it (which would also be a faster solution, but won't work cross different fs). Can you please give me some examples of what it breaks? (just for a sake of having a specific use case) --- Additional comment from chaowang on 2012-08-09 22:31:01 EDT --- Lots of customers would like to search /var/crash for their vmcores, and obviously abrt-vmcore breaks the law that kdump setup, which makes confusion. They also filed bugs on this issue, bug 844679. And perhaps, use a softlink instead?
Fixed in git: commit f228de8d5967d819fd94a0161de1382b0af147a3 Author: Denys Vlasenko <vda.linux> Date: Mon Aug 13 12:49:50 2012 +0200 abrt-harvest-vmcore: add CopyVMcore config option to copy vmcores
Cause ABRT was moving kernel cores from it's default location /var/crash to /var/spool/abrt Consequence Various tools relying on the default location (/var/crash) were broken. Fix Don't move the core, just copy them Result The kernel cores are not moved from /var/crash
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0290.html