Sorry, I am a new to this.
1. Is a search available for the mailing list? Couldn't find one.
2. /var/cache/abrt consumes 650 MB of disk space. Can I delete this?
Thanks for any answer.
Maximilian
02.11.2010, 01:29, "Maximilian Eberl" maximilianeberl@yahoo.de:
Sorry, I am a new to this.
- Is a search available for the mailing list? Couldn't find one.
Hi, Maximilian.
There is the archive where you can download all traffic and use the local search tool available on your system. https://fedorahosted.org/pipermail/crash-catcher/
- /var/cache/abrt consumes 650 MB of disk space. Can I delete this?
I'm not sure on that one, so let's see what the developers say.
I'm not sure on that one, so let's see what the developers say.
Hi, I already replied, but must have pressed the wrong button, so it went directly to Max. Resending the message so others can find the answer.
On 11/01/2010 06:29 PM, Maximilian Eberl wrote:
Sorry, I am a new to this.
- Is a search available for the mailing list? Couldn't find one.
I don't know about any, sorry ..
- /var/cache/abrt consumes 650 MB of disk space. Can I delete this?
Thanks for any answer.
Maximilian
ABRT shouldn't use that directory since version 1.1.12, so it should be safe to remove it (the data there are probably some stalled data after some update), but more cleaner solution is to run abrt-gui and remove all the entries (you can try to run it with root privileges to see all of the crashes) and then remove just the content of /var/cache/abrt not the directory itself since it's still owned by the abrt rpm which is probably a bug, that need to be fixed.
Hope this helps, Jirka
On Mon, 2010-11-01 at 17:29 +0000, Maximilian Eberl wrote:
Sorry, I am a new to this.
- Is a search available for the mailing list? Couldn't find one.
Probably not.
- /var/cache/abrt consumes 650 MB of disk space. Can I delete this?
Yes. Newer versions of abrt use more correct location of /var/spool/abrt for its crash dump directories. If you have newer version, you may have old, unused crash dumps in /var/spool/abrt. Delete them by hand.
Normally, though, you should delete crashes through GUI or CLI, not by hand. Otherwise database gets out of sync (not fatal, just "wrong").
crash-catcher@lists.fedorahosted.org