Abrtd is apparently an "automated bug reporting tool's daemon", but the manual is very brief, and to be honest, I'm not really interested in spending time getting to know it myself.
So I'm thinking I might as well turn it off UNLESS it serves a useful purpose. Eg, I just had a crash which was reported in /var/log/messages:
kernel: [ 2581.081587] BUG: unable to handle kernel paging request at 0000000000010051
Unless I see this kind of thing repeatedly causing a problem, I cannot be bothered to investigate it. However, I notice that it gets passed to abrtd, which takes some kind of action:
Jun 17 09:04:55 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
Jun 17 09:04:55 abrtd: Directory 'kerneloops-1308315895-1227-1' creation detected
Jun 17 09:04:55 abrtd: New crash /var/spool/abrt/kerneloops-1308315895-1227-1, processing
Jun 17 09:04:55 abrtd: Registered Action plugin 'RunApp'
Jun 17 09:04:55 abrtd: RunApp('/var/spool/abrt/kerneloops-1308315895-1227-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
My question is: does anyone know if abrtd by default actually reports this to the outside? If not, it is completely pointless, because like I said, I cannot be bothered learning to use it for such purpose, and I might as well disable it. On the other hand, if it does do this, then it would be doing something useful and I'll leave it on.