|
Packit |
8ea169 |
abrt-auto-reporting(1)
|
|
Packit |
8ea169 |
======================
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
NAME
|
|
Packit |
8ea169 |
----
|
|
Packit |
8ea169 |
abrt-auto-reporting - Get or modify the auto reporting option values
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
SYNOPSIS
|
|
Packit |
8ea169 |
--------
|
|
Packit |
8ea169 |
'abrt-auto-reporting' [-v] [ enabled | yes | 1 | on | disabled | no | 0 | off ]
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
DESCRIPTION
|
|
Packit |
8ea169 |
-----------
|
|
Packit |
8ea169 |
Reads the configuration from abrt.conf and saves the changes to the same file.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
The changes will take effect immediately without necessity to restart any ABRT
|
|
Packit |
8ea169 |
process and will be persistent.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
'disabled'::
|
|
Packit |
8ea169 |
User have to report the detect problems manually
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
'enabled'::
|
|
Packit |
8ea169 |
ABRT uploads an uReport which was generated for a detected problem
|
|
Packit |
8ea169 |
immediately after the detection phase.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
uReport description
|
|
Packit |
8ea169 |
~~~~~~~~~~~~~~~~~~~
|
|
Packit |
8ea169 |
ABRT supports uReports for four types of crashes: crashes of C/C++ programs
|
|
Packit |
8ea169 |
that result in a core dump, uncaught Python exceptions, uncaught Java
|
|
Packit |
8ea169 |
exceptions and kernel oopses.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
Each uReport generally contains a stack trace, or multiple stack traces in the
|
|
Packit |
8ea169 |
case of multi-threaded C/C++ and Java programs. The stack trace only describes
|
|
Packit |
8ea169 |
the call stack of the program at the time of the crash and does not contain
|
|
Packit |
8ea169 |
contents of any variables.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
Every uReport also contains identification of the operating system, versions of
|
|
Packit |
8ea169 |
the RPM packages involved in the crash, and whether the program ran under a
|
|
Packit |
8ea169 |
root user.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
There are also items specific to each crash type:
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
C/C++ crashes::
|
|
Packit |
8ea169 |
these are path to the executable and signal delivered to the program,
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
Python exceptions::
|
|
Packit |
8ea169 |
there is the type of the exception (without the error message, which may
|
|
Packit |
8ea169 |
contain sensitive data),
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
for kernel oopses::
|
|
Packit |
8ea169 |
these are list of loaded kernel modules, list of taint flags, and full text
|
|
Packit |
8ea169 |
of the kernel oops.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
'Warning':
|
|
Packit |
8ea169 |
The full text of a kernel oops might contain information like the
|
|
Packit |
8ea169 |
identification of the host hardware type. You should disable the autoreporting
|
|
Packit |
8ea169 |
feature if you do not want to share this information with Red Hat.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
OPTIONS
|
|
Packit |
8ea169 |
-------
|
|
Packit |
8ea169 |
-v, --verbose::
|
|
Packit |
8ea169 |
Be more verbose. Can be given multiple times.
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
SEE ALSO
|
|
Packit |
8ea169 |
--------
|
|
Packit |
8ea169 |
abrt.conf(5)
|
|
Packit |
8ea169 |
|
|
Packit |
8ea169 |
AUTHORS
|
|
Packit |
8ea169 |
-------
|
|
Packit |
8ea169 |
* ABRT team
|