+++ 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):
Steps to Reproduce:
--- Additional comment from email@example.com 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 firstname.lastname@example.org 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:
Author: Denys Vlasenko <email@example.com>
Date: Mon Aug 13 12:49:50 2012 +0200
abrt-harvest-vmcore: add CopyVMcore config option to copy vmcores
ABRT was moving kernel cores from it's default location /var/crash to /var/spool/abrt
Various tools relying on the default location (/var/crash) were broken.
Don't move the core, just copy them
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.