Hide Forgot
by default in RHEL 6, ABRT doesn't enable any reporters, which means that data center users (who aren't running X) won't be notified when ABRT catches a problem. I'd suggest we at least enable the mailx reporter by default...
(In reply to comment #0) > > I'd suggest we at least enable the mailx reporter by default... You mean enable automatic reporting using mailx by default?
yeah, I'd suggest both mailing and logging by default, although are you guys using syslog? I've noticed we're not getting ABRT reports from CLI environments, and I think it's because we're not notifying sysadmins through any of their normal communication channels.
We need to move abrt-plugin-mailx into @base in comps, the rest is just change in config file -#ActionsAndReporters = Mailx("[abrt] new crash was detected") +ActionsAndReporters = Mailx("[abrt] new crash was detected")
How to test: $ sleep 100& $ kill -s SEGV $! - there should be email about the crash in root@localhost
will this send to syslog as well or should I spin out a new (6.2) request?
> will this send to syslog as well or should I spin out a new (6.2) request? ABRT already sends a message to syslog when it detects a crash: Mar 14 12:44:50 dhcp-25-200 abrt[28009]: saved core dump of pid 27973 (/bin/sleep) to /var/spool/abrt/ccpp-2011-03-14-12:44:50-27973.new/coredump (372736 bytes) Mar 14 12:44:50 dhcp-25-200 abrtd: New crash /var/spool/abrt/ccpp-2011-03-14-12:44:50-27973, processing is this enough or would you like to see something else in syslog?
looks great, thanks Jiri
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0619.html