Red Hat Bugzilla – Bug 811733
abrt: Do not move kernel vmcore out of /var/crash/
Last modified: 2012-08-29 20:59:05 EDT
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:
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)
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 <firstname.lastname@example.org>
Date: Mon Aug 13 12:47:15 2012 +0200
abrt-harvest-vmcore: add CopyVMcore config option to copy vmcores
abrt-2.0.12-1.fc17, libreport-2.0.13-1.fc17, btparser-0.18-2.fc17 has been submitted as an update for Fedora 17.
Package abrt-2.0.12-1.fc17, libreport-2.0.13-1.fc17, btparser-0.18-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.12-1.fc17 libreport-2.0.13-1.fc17 btparser-0.18-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
abrt-2.0.12-1.fc17, libreport-2.0.13-2.fc17, btparser-0.18-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.