The Linux Manuals (man pages) document is an important part of Linux documents. Linux Manuals are organized as several sections. Each section has a group of commands for a specific area in Linux usage, administration or development.
abrt-install-ccpp-hook – Install coredump handler. Synopsisabrt-install-ccpp-hook install | uninstall | is-installed Descriptionabrt-install-ccpp-hook registers ABRT coredump handler (which saves segfault data) into kernel. Optionsinstall Install coredump handler. uninstall Uninstall coredump handler. is-installed Returns 0 if handler is installed, otherwise 1.Authors• ABRT team
abrt-harvest-vmcore – Converts VMCores to ABRT problems Synopsisabrt-harvest-vmcore DescriptionThis script is meant to be run once at system startup after abrtd is up and running. It moves all vmcore directories in /var/crash (which are presumably created by kdump) to abrtd spool directory. The goal is to let abrtd notice and process them as new problem…
abrt-harvest-pstoreoops – Reconstruct oops from /sys/fs/pstore/* files, create ABRT problems and remove the files Synopsisabrt-harvest-pstoreoops DescriptionThis script is meant to be run once at system startup after abrtd is up and running. It scans /sys/fs/pstore/*, reconstructs oops text(s) from these files, creates ABRT problem directories from them, then removes the files (pstore storage is a…
abrt-handle-upload – Unpacks and moves problem data. Synopsisabrt-handle-upload ABRT_DIR UPLOAD_DIR FILENAME DescriptionThe tool unpacks FILENAME located in UPLOAD_DIR and moves the problem data found in it to ABRT_DIR. It supports unpacking tarballs compressed by gzip, bzip2 or xz. It’s called by abrtd when a new file is noticed in the upload directory configured by the…
abrt-dump-xorg – Extract Xorg crash from FILE (or standard input) Synopsisabrt-dump-xorg [-vsoxm] [-d DIR]/[-D] [FILE] DescriptionThis tool creates problem directory from or prints Xorg crash extracted from FILE or standard input. Options-v, –verbose Be more verbose. Can be given multiple times. -s Log to syslog -o Print found crash data on standard output -d DIR…
abrt-dump-oops – Extract oops from FILE (or standard input) Synopsisabrt-dump-oops [-vusoxtm] [-d DIR]/[-D] [FILE] DescriptionThis tool creates problem directory from, updates problem directory with or prints oops extracted from FILE or standard input. Files/etc/abrt/plugins/oops.conf Configuration file where user can disable detection of non-fatal MCEsOptions-v, –verbose Be more verbose. Can be given multiple times. -s Log…
abrt-cli – List, remove, print, analyze, report problems Synopsisabrt-cli [–authenticate] COMMAND [COMMAND OPTIONS] abrt-cli list [-vn] [–detailed] [–since NUM] [–until NUM] [DIR]… abrt-cli remove [-v] DIR… abrt-cli report [-v] [–delete] DIR… abrt-cli info [-v] [–detailed] [-s SIZE] DIR… abrt-cli status [-vb] [–since NUM] abrt-cli process [-v] [–since NUM] DIR… Global Options-a,–authenticate Enable PolicyKit authentication to…
abrt-bodhi – The ABRT bodhi client. Synopsisabrt-bodhi [-v] [-r[RELEASE]] (-b ID1[,ID2,…] | PKG-NAME) [PKG-NAME]… Descriptionabrt-bodhi is the command-line tool for listing a new updates. Bodhi can be queried by release, bug id or package name. Options-v, –verbose Be verbose -r[RELEASE], –release[RELEASE] Specify a release (f16|rawhide) -b, –bugs ID1,ID2,.. Specify any number of Bugzilla IDs (–bugs=1234,5678)…
abrt-backtrace – a backtrace analyzer for abrt Synopsisabrt-backtrace [option]… [FILE] Descriptionabrt-backtrace is a command line tool that analyzes backtraces produced by GDB and provides their textual representation useful for crash duplication detection. By default, abrt-backtrace prints the backtrace tree created by parsing the input file. OptionsBasic startup options -V, –version Displays version of abrt-backtrace. -?,…
abrt-auto-reporting – Get or modify the auto reporting option values Synopsisabrt-auto-reporting [-v] [ enabled | yes | 1 | on | disabled | no | 0 | off ] DescriptionReads the configuration from abrt.conf and saves the changes to the same file. The changes will take effect immediately without necessity to restart any ABRT process…
abrt-applet – Applet which notifies user when new problems are detected by ABRT Synopsisabrt-applet [-v] DescriptionThis tool listens on org.freedesktop.problems D-Bus bus and waits for Crash signal. When the tool detects the signal, it notifies user about new problem over a desktop specific notification pop-up. At start-up this tool checks for new problems which occurred…
abrt-action-trim-files – Deletes old problem directories or files in specified directories until they are smaller than specified size. Synopsisabrt-action-trim-files [-v] [-d SIZE:DIR]… [-f SIZE:DIR]… [-p DIR] [FILE]… Options-v Be more verbose. Can be given multiple times. -d SIZE:DIR Delete problem directories in DIR. SIZE can be suffixed by k,m,g,t to specify kilo,mega,giga,terabytes. -f SIZE:DIR Delete…
abrt-action-save-package-data – Query package database and save package and component name. Synopsisabrt-action-save-package-data [-v] [-c CONFFILE] -d DIR DescriptionThe tool reads problem directory DIR. It analyzes contents of analyzer, executable, cmdline and remote elements, checks database of installed packages, and creates new elements package and component. This data is usually necessary if the problem will be…
abrt-action-save-kernel-data – Creates uReport mandatory files for kernel oopses. Synopsisabrt-action-save-kernel-data DescriptionThe tool reads problem directory DIR. It analyzes contents of kernel element, checks database of installed packages, and creates new elements pkg_name, pkg_arch, pkg_version, pkg_release. These files are required by reporter-ureporter (mandatory in uReport). Integration with ABRT eventsThis tool can be used as an ABRT…
abrt-action-perform-ccpp-analysis – Allows users to select acceptable way of core dump analysis Synopsisabrt-action-perform-ccpp-analysis [-h] [-d PROBLEM_DIR] DescriptionThis tool allows user to select between local and remote core dump analysis. The local analysis may require to download huge amount of data but is completely safe. On the contrary the remote analysis only needs to upload the…
abrt-action-notify – Announces a new occurrence of problem via all accessible channels Synopsisabrt-action-notify [-h] -d PROBLEM_DIR [-v] [-a] [-e AUTOREPORTING_EVENT] DescriptionThe current implementation emits a D-Bus signal on System bus in path /org/freedesktop/problems of org.freedesktop.problems interface for Crash member. Integration with ABRT eventsabrt-action-notify is used to notify new problems and consecutive occurrences of a single…
abrt-action-list-dsos – Prints out DSO from mapped memory regions. Synopsisabrt-action-list-dsos [-o OUTFILE] -m PROC_PID_MAP_FILE DescriptionThe tool reads a file containing the mapped memory regions. Output is printed to stdout or file. Output format: %p %n %v %i where %p path to library or binary file, which is mapped in memory region %n name, version, release,…
abrt-action-install-debuginfo – Install debuginfos for build-ids Synopsisabrt-action-install-debuginfo [-vy] [–ids=BUILD_IDS_FILE] [–tmpdir=TMPDIR] [–cache=CACHEDIR[:DEBUGINFODIR1:DEBUGINFODIR2…]] [–size_mb=SIZE] [-e PATH] DescriptionInstalls debuginfos for all build-ids listed in BUILD_IDS_FILE to CACHEDIR, using TMPDIR as temporary staging area. Old files in CACHEDIR are deleted until it is smaller than SIZE. Options-v Be more verbose. Can be given multiple times. -y Noninteractive, assume Yes…
abrt-action-generate-core-backtrace – Generates coredump-level backtrace Synopsisabrt-action-generate-core-backtrace [-v] [-r] [-d DIR] DescriptionThis tool uses coredump from the file coredump and binary at the path stored in file executable in the problem directory to generate coredump-level backtrace. Coredump-level backtrace resembles ordinary backtrace in that it contains information about call frames present on the stack at the time…
abrt-action-generate-backtrace – Analyzes coredump, generates and saves backtrace. Synopsisabrt-action-generate-backtrace [-v] [-d DIR] [-i DIR1[:DIR2]…] [-t NUM] DescriptionThis tool runs gdb(1) on a file named coredump in problem directory DIR. gdb(1) generates backtrace and other diagnostic information about the state of the application at the moment when coredump was generated. Then the tool saves it as…