diff options
| -rw-r--r-- | doc/PLUGINS-HOWTO | 62 | ||||
| -rw-r--r-- | lib/Plugins/abrt-Bugzilla.7 | 16 | ||||
| -rw-r--r-- | lib/Plugins/abrt-FileTransfer.7 | 45 | ||||
| -rw-r--r-- | lib/Plugins/abrt-KerneloopsReporter.7 | 6 | ||||
| -rw-r--r-- | lib/Plugins/abrt-KerneloopsScanner.7 | 10 | ||||
| -rw-r--r-- | lib/Plugins/abrt-Logger.7 | 12 | ||||
| -rw-r--r-- | lib/Plugins/abrt-Mailx.7 | 16 | ||||
| -rw-r--r-- | lib/Plugins/abrt-RunApp.7 | 12 | ||||
| -rw-r--r-- | lib/Plugins/abrt-SQLite3.7 | 12 | ||||
| -rw-r--r-- | lib/Plugins/abrt-plugins.7 | 24 | ||||
| -rw-r--r-- | src/Daemon/abrt.8 | 20 | ||||
| -rw-r--r-- | src/Daemon/abrt.conf.5 | 45 |
12 files changed, 141 insertions, 139 deletions
diff --git a/doc/PLUGINS-HOWTO b/doc/PLUGINS-HOWTO index bb315f99..a8eb4e20 100644 --- a/doc/PLUGINS-HOWTO +++ b/doc/PLUGINS-HOWTO @@ -1,44 +1,44 @@ This document describes how to create your own plugin for abrt. -There is a base abstract class CPlugin, but you can't inherit -directly from that: you have to use one of the four subclasses, -depending on what is your plugin supposed to do. +Although a base abstract class CPlugin exists, you can't inherit +directly from it. You must use one of the four subclasses, +depending on what you want your plugin to do. -These are the subclasses: +The subclasses are: * Action plugin (CAction) * Analyzer plugin (CAnalyzer) * Reporter plugin (CReporter) * Database plugin (CDatabase) -Each of them requires you to override different set of methods. +Each of them requires you to override a different set of methods. -One very common parameter of the methods is called -pDebugDumpDir: it specifies the directory, -which is created to gather information of this specific crash: -the files (such as core dumps) that were created when the application -crashed are all stored here. In addition, the plugins can write +The pDebugDumpDir parameter is very common: it specifies the directory +that is created to gather information of this specific crash. +The files that were created when the application crashed (such as core dumps) +are all stored here. In addition, the plugins can write their output files there, if any. Let's discuss the plugin types in detail: Action Plugin ------------- -This type of plugin is used, when you need some action to be -performed in the case the crash is encountered. +You use this type of plugin when you need some action to be +performed when a crash is encountered. you have to override one method: virtual void Run(const std::string& pActiveDir, const std::string& pArgs) = 0; -This method runs the specified action. - The first argument is an directory name. It can be either current debug - dump dir or directory which contains all debug dumps. + The first argument is a directory name. It can be either the current debug + dump dir or a directory that contains all debug dumps. The second argument is a string with arguments specified for the action. Analyzer Plugin --------------- -This plugin has to compute the UUID of the crash: crashes in kernel, -in userspace binary, in python script etc. differ, so you have to have -plugin for each type of application, that you want "abrt" to handle. +This plugin has to compute the UUID of the crash. Crashes differ, depending on +where they occur, for example crashes in the kernel differ from crashes in +userspace binaries, which differ from crashes in python scripts. Therefore, +you need a plugin for each type of application that you want "abrt" to handle. you have to override these methods: @@ -48,8 +48,8 @@ virtual std::string GetLocalUUID(const std::string& pDebugDumpPath) = 0; virtual std::string GetGlobalUUID(const std::string& pDebugDumpPath) = 0; - This method computes the global UUID of the crash. -NOTE:The difference between local and global UUID is, that the local UUID -is specific for the machine architecture, on which the crash is encountered. +NOTE:The difference between local and global UUID is that the local UUID +is specific for the machine architecture on which the crash is encountered. When the crash is reported, abrt has to use the "-debuginfo" packages to render a global UUID, which should be independent of the specific system (the same crash on different architectures/configurations can @@ -69,18 +69,17 @@ you have to override this method: virtual void Report(const crash_report_t& pCrashReport, const std::string& pArgs) = 0; --It's self-explanatory, that this method takes the report +-It is self-explanatory, that this method takes the report and presents it somewhere to the world. - The second argument is a string with arguments specified for the retorter. + The second argument is a string with arguments specified for the reporter. Database Plugin --------------- -This plugin is used to store the metadata about the crash: -they have to be in the database in order to distinguish, -whether the current crash is or is not the same as some -crash before. The database can be local, or in some -centralized location on the network. +You use this plugin to store the metadata about the crash. The metadata +has to be in a database, to distinguish whether the current crash is or +is not the same as some crash before. The database can be local, or in +some centralized location on the network. you have to override these methods: virtual void Connect() = 0; @@ -91,14 +90,14 @@ virtual void Insert(const std::string& pUUID, const std::string& pUID, const std::string& pDebugDumpPath, const std::string& pTime) = 0; -- insert an entry to the database: you use both UID (user ID) and UUID +- insert an entry into the database: you use both UID (user ID) and UUID (ID of the crash) virtual void Delete(const std::string& pUUID, const std::string& pUID) = 0; - delete an entry virtual void SetReported(const std::string& pUUID, const std::string& pUID) = 0; -- insert to the database the information, that this bug was already +- insert information into the database to say that this bug was already reported (so for example the report plugins won't run several times for the same bug) @@ -112,11 +111,10 @@ virtual const database_row_t GetUUIDData(const std::string& pUUID, const The macro PLUGIN_INFO --------------------- -It is required, in order for your subclass to be properly registered -and treated as a plugin, to use the macro PLUGIN_INFO in your plugin's -header file. +Use the macro PLUGIN_INFO in the header file of your plugin so that your +subclass will be properly registered and treated as a plugin. This sets up all the lower-level and administrative details to fit your -class into the plugin infrastructure. The syntax is this: +class into the plugin infrastructure. The syntax is: PLUGIN_INFO(type, plugin_class, name, version, description, email, www) - "type" is one of ANALYZER, ACTION, REPORTER, or DATABASE diff --git a/lib/Plugins/abrt-Bugzilla.7 b/lib/Plugins/abrt-Bugzilla.7 index ec56256d..c3c0e902 100644 --- a/lib/Plugins/abrt-Bugzilla.7 +++ b/lib/Plugins/abrt-Bugzilla.7 @@ -4,22 +4,22 @@ Bugzilla plugin for abrt(8) .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes the \fIBugzilla\fP plugin +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes the \fIBugzilla\fP plugin for \fIabrt\fP. .P -This plugin is used to report the crash to the Bugzilla. The plugin -will determine the package name and distribution version. The crash -data is attached to the bug report. +This plugin is used to report the crash to a Bugzilla instance. The +plugin will determine the package name and distribution version. The +crash data is attached to the bug report. .SH INVOCATION The plugin is invoked in the \fIabrt.conf\fP configuration file. No parameters are necessary. .SH CONFIGURATION The \fIBugzilla.conf\fP configuration file contains several -entries in a format "Option = Value". The options are: +entries in the format "Option = Value". The options are: .SS BugzillaURL -The URL of the Bugzilla instance you want to use, including the +The URL of the Bugzilla instance that you want to use, including the path to the xmlrpc. The default is https://bugzilla.redhat.com/xmlrpc.cgi .SS Login Your Bugzilla login. If you have no Bugzilla account, you cannot diff --git a/lib/Plugins/abrt-FileTransfer.7 b/lib/Plugins/abrt-FileTransfer.7 index c2c2ac7b..b126c2c9 100644 --- a/lib/Plugins/abrt-FileTransfer.7 +++ b/lib/Plugins/abrt-FileTransfer.7 @@ -4,58 +4,59 @@ FileTransfer plugin for abrt(8) .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes the \fIFileTransfer\fP plugin +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes the \fIFileTransfer\fP plugin for \fIabrt\fP. .P This plugin is used to transfer the crash report to another -machine via some file transfer protocol. Supported protocols -are FTP, FTPS, HTTP, HTTPS, SCP, SFTP and TFTP. +machine using a file transfer protocol. The protocols supported +are FTP, FTPS, HTTP, HTTPS, SCP, SFTP, and TFTP. .SH INVOCATION .P The plugin is invoked in the \fIabrt.conf\fP file, usually in the \fIActionsAndReporters\fP option and/or the \fI[cron]\fP section. -There are two modes of invocation: either you use the parameter -\fI"store"\fP: in this case, the plugin stores the information, -that the crash occurs, in its internal list. +There are two modes of invocation: .P -If you use some other parameter, or no parameter at all, the +* If you use the parameter +\fI"store"\fP, the plugin stores a record of the occurrence of +the crash in its internal list. +.P +* If you use some other parameter, or no parameter at all, the plugin will iterate through the internal list and will send every recorded crash to the server specified in the \fIFileTransfer.conf\fP configuration file. After that, the internal list is cleared. .P -The rationale of this behavior is this: on a production -machine, you probably don't want the crash data to be -sent in the time the machine is busy working, you want -to send everything in some more quiet time (at night, perhaps) -and schedule this in the \fI[cron]\fP section of \fIabrt.conf\fP. +On a production machine, you probably do not want the daemon to send crash +data at times that the machine is busy working. This second mode allows you +to send crash reports at a quieter time (at night, perhaps) that you +schedule in the \fI[cron]\fP section of \fIabrt.conf\fP. .SH CONFIGURATION The \fIFileTransfer.conf\fP configuration file contains -several entries in a format "Option = Value". The options are: +several entries in the format "Option = Value". The options are: .SS URL The URL of the server, where the crash should be transfered, specifying the protocol, the path, -the user name and the password, for example +the user name and the password, for example: .br URL = ftp://user:passwd@server.com/path .SS ArchiveType -The type of the archive, where the crash data will be packed. -Currently supporting \fI.tar.gz\fP, \fI.tar.bz2\fP and \fI.zip\fP +The type of the archive in which to pack the crash data. +Currently, \fI.tar.gz\fP, \fI.tar.bz2\fP and \fI.zip\fP are supported. The plugin currently relies on external file archiving commandline utilities, which will create the archive. The default is .br ArchiveType = .tar.gz .SS RetryCount -This specifies, how many times will the plugin try to resend -the file in the case the transfer was not succesful. The plugin +This specifies how many times the plugin will try to resend +the file if the transfer was not succesful. The plugin waits a while before it retries the transfer: see \fIRetryDelay\fP The default is .br RetryCount = 3 .SS RetryDelay -In the case the transfer was not succesful, the plugin will +If the transfer was not succesful, the plugin will wait some time before sending the file again. This configuration option specifies the time in seconds. The default is .br @@ -63,7 +64,7 @@ RetryDelay = 20 .SH EXAMPLES .P Typical configuration in \fIabrt.conf\fP. The crash is stored -each time it happens and on midnight, all the crash data +each time it happens and at midnight, all the crash data is transferred to a central server. .P [common] diff --git a/lib/Plugins/abrt-KerneloopsReporter.7 b/lib/Plugins/abrt-KerneloopsReporter.7 index a0c2341d..e0d32c35 100644 --- a/lib/Plugins/abrt-KerneloopsReporter.7 +++ b/lib/Plugins/abrt-KerneloopsReporter.7 @@ -4,9 +4,9 @@ KerneloopsReporter plugin for abrt(8) .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes the \fIKerneloopsReporter\fP +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes the \fIKerneloopsReporter\fP plugin for \fIabrt\fP. .P This plugin is used to report the crash to the Kerneloops tracker. diff --git a/lib/Plugins/abrt-KerneloopsScanner.7 b/lib/Plugins/abrt-KerneloopsScanner.7 index 0cbc1dcc..d9642a97 100644 --- a/lib/Plugins/abrt-KerneloopsScanner.7 +++ b/lib/Plugins/abrt-KerneloopsScanner.7 @@ -4,16 +4,16 @@ KerneloopsScanner plugin for abrt(8) .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes the \fIKerneloopsScanner\fP +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes the \fIKerneloopsScanner\fP plugin for \fIabrt\fP. .P This plugin reads the system log file (default /var/log/messages) and stores the kernel oops crashes, which were not already -reported, to the abrt's debug dump directory. +reported, to abrt's debug dump directory. .P -In order to distinguish between new crashes and the crashes +To distinguish between new crashes and crashes that were already reported, the plugin makes its own entry in the log file, which acts as a separator. .SH INVOCATION diff --git a/lib/Plugins/abrt-Logger.7 b/lib/Plugins/abrt-Logger.7 index 6541c104..0f814d24 100644 --- a/lib/Plugins/abrt-Logger.7 +++ b/lib/Plugins/abrt-Logger.7 @@ -4,17 +4,17 @@ Logger plugin for abrt(8) .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes the \fILogger\fP plugin +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes the \fILogger\fP plugin for \fIabrt\fP. .P This plugin is used to log the crash to a file. .P The log will contain all the file names as well as their content. It also contains "duplicity check": the ID -of the crash, which is used to tell, if the same -crash already happened. +of the crash, which is used to tell whether the same +crash has happened previously. .SH INVOCATION The plugin is invoked in the \fIabrt.conf\fP configuration file. No parameters are necessary. @@ -24,7 +24,7 @@ several entries in a format "Option = Value". The options are: .SS LogPath The path to the log file. .SS AppendLogs -If set to "yes", which is the default, \fILogger\fP will append +If set to "yes" (the default) \fILogger\fP will append the report to the file, otherwise it will overwrite the file (so only the last crash will be stored). .SH EXAMPLES diff --git a/lib/Plugins/abrt-Mailx.7 b/lib/Plugins/abrt-Mailx.7 index 43790f24..10d5e4b8 100644 --- a/lib/Plugins/abrt-Mailx.7 +++ b/lib/Plugins/abrt-Mailx.7 @@ -4,9 +4,9 @@ Mailx plugin for abrt(8) .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes the \fIMailx\fP plugin +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes the \fIMailx\fP plugin for \fIabrt\fP. .P This plugin is used to mail the data about the crash @@ -25,13 +25,13 @@ The \fIMailx\fP plugin executes the external "mailx" command to send the mail. This option defines some additional command line parameters, which should be added to the program invocation, if any. .SS EmailFrom -The address, from which the e-mail is sent. +The address from which the email is sent. .SS EmailTo -The address, to which the e-mail is sent. +The address to which the email is sent. .SS SendBinaryData -Can be "yes" or "no". If set to "yes", the e-mail will contain -also the binary files associated with the crash. Warning: -this can cause the e-mails to be large! (several MB) +Can be "yes" or "no". If set to "yes", the email will also +contain the binary files associated with the crash. Warning: +this can cause the emails to be large! (several MB) .SH EXAMPLES .P These are snippets from the \fIabrt.conf\fP configuration file. diff --git a/lib/Plugins/abrt-RunApp.7 b/lib/Plugins/abrt-RunApp.7 index 2128cf8a..6d75b12c 100644 --- a/lib/Plugins/abrt-RunApp.7 +++ b/lib/Plugins/abrt-RunApp.7 @@ -4,15 +4,15 @@ RunApp plugin for abrt(8) .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes the \fIRunApp\fP plugin +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes the \fIRunApp\fP plugin for \fIabrt\fP. .P -This plugin is used to run an arbitrary application, when the crash occurs. +This plugin is used to run a specified application when the crash occurs. .SH INVOCATION The plugin is invoked in the \fIabrt.conf\fP configuration file. -The first parameter is the command to run, the second, optional +The first parameter is the command to run. The second, optional parameter specifies an output file, to which the standard output of the program is saved. .SH CONFIGURATION @@ -22,7 +22,7 @@ sufficient. .P These are snippets from the \fIabrt.conf\fP configuration file. .P -1) each time something crashes, print (and save in a text file) +1) Each time something crashes, print (and save in a text file) which processes are running on the system. .PP [common] diff --git a/lib/Plugins/abrt-SQLite3.7 b/lib/Plugins/abrt-SQLite3.7 index 86b5097f..87df539f 100644 --- a/lib/Plugins/abrt-SQLite3.7 +++ b/lib/Plugins/abrt-SQLite3.7 @@ -4,15 +4,15 @@ SQLite3 database plugin for abrt(8) .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes the \fISQLite3\fP database plugin +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes the \fISQLite3\fP database plugin for \fIabrt\fP. .P -This is a database plugin: \fIabrt\fP needs some database to store -its metadata. You can choose which one, specifying "Database" in +This is a database plugin: \fIabrt\fP needs a database in which to store +its metadata. You can choose one by specifying "Database" in the \fIabrt.conf\fP configuration file. Currently SQLite3 is -the only choice. +the only choice supported. .SH INVOCATION The plugin is invoked in the \fIabrt.conf\fP configuration file, like this: diff --git a/lib/Plugins/abrt-plugins.7 b/lib/Plugins/abrt-plugins.7 index 22f89d68..a7c185cc 100644 --- a/lib/Plugins/abrt-plugins.7 +++ b/lib/Plugins/abrt-plugins.7 @@ -4,28 +4,28 @@ abrt-plugins \- plugins for the abrt crash reporter program .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, +is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) -and performs some actions according to the type of application that -crashed and according to configuration in the +and takes action according to the type of application that +crashed and according to the configuration specified in the .I abrt.conf configuration file. .P -There are plugins for various actions: for example reporting -the crash to Bugzilla, mailing the report, transfering the -report via FTP or SCP, or running an arbitrary program. +Plugins allow abrt to perform various actions: for example, +to report the crash to Bugzilla, to mail the report, to transfer +the report via FTP or SCP, or to run a program that you specify. .P -This manual page provides a list of all manual pages of -the plugins. +This manual page provides a list of all the manual pages for +these plugins. .P -If you want to create your own plugin, there's a PLUGINS-HOWTO +If you want to create your own plugin, refer to the PLUGINS-HOWTO file in the documentation directory. .SH INVOCATION Each plugin is invoked in the \fIabrt.conf\fP configuration -file, in the section, which is appropriate to what you -want to do. +file, in the section that is appropriate to what you +want abrt to do. .SH CONFIGURATION -Almost each plugin has its configuration file, +Almost every plugin has its configuration file, stored in the \fI/etc/abrt/plugins\fP directory. .SH "SEE ALSO" .IR abrt (8), diff --git a/src/Daemon/abrt.8 b/src/Daemon/abrt.8 index 1317a891..f3ae1279 100644 --- a/src/Daemon/abrt.8 +++ b/src/Daemon/abrt.8 @@ -5,13 +5,13 @@ abrt \- an automated bug-reporting tool .B abrt [ -d ] .SH DESCRIPTION .I abrt -is a daemon which watches for application crashes. When a crash occurs, +is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) -and performs some actions according to the type of application that -crashed and according to configuration in the +and takes action according to the type of application that +crashed and according to the configuration in the .I abrt.conf -config file. There are plugins for various actions: for example reporting -the crash to Bugzilla, mailing the report, transfering the +config file. There are plugins for various actions: for example to report +the crash to Bugzilla, to mail the report, or to transfer the report via FTP or SCP. See the manual pages for the respective plugins. .SH OPTIONS @@ -22,13 +22,13 @@ respective plugins. This option causes .I abrt -to print some more debugging information, when the daemon is started. +to print more debugging information when the daemon is started. .SH CAVEATS -When you use some other crash catching tool, specific for an aplication +When you use some other crash-catching tool, specific for an application or an application type (for example BugBuddy for GNOME applications), -the crashes of this type will be handled by this application and -not \fIabrt\fP. If you don't want this behavior, turn the higher-level crash -catching application off: the crashes will be handled by \fIabrt\fP then. +crashes of this type will be handled by that tool and +not by \fIabrt\fP. If you want \fIabrt\fP to handle these crashes, +turn off the higher-level crash-catching tool. .SH "SEE ALSO" .IR abrt.conf (5), .IR abrt-plugins (7) diff --git a/src/Daemon/abrt.conf.5 b/src/Daemon/abrt.conf.5 index 481b4f5f..edccb596 100644 --- a/src/Daemon/abrt.conf.5 +++ b/src/Daemon/abrt.conf.5 @@ -4,13 +4,13 @@ abrt.conf \- configuration file for abrt .SH DESCRIPTION .P .I abrt -is a daemon which watches for application crashes. When a crash occurs, -it collects the crash data and performs some actions according to -the configuration. This manual page describes \fIabrt\fP's configuration +is a daemon that watches for application crashes. When a crash occurs, +it collects the crash data and takes action according to +its configuration. This manual page describes \fIabrt\fP's configuration file. .P The configuration file consists of sections, each section contains -several items in a format "Option = Value". The description of each +several items in the format "Option = Value". A description of each section follows: .SS [Common] .TP @@ -21,49 +21,52 @@ will report crashes only in GPG signed packages. When set to "no", it will report crashes also in unsigned packages. .TP .B OpenGPGPublicKeys = \fIfilename\fP , \fIfilename\fP ... -This is the place, where you specify the trusted GPG keys, with -which the packages have to be signed for "EnableOpenGPG = yes". +These are the trusted GPG keys with which packages have to be +signed for +.I abrt +to report them if "EnableOpenGPG = yes". .TP .B BlackList = \fIpackageName\fP, \fIpackageName\fP ... -Packages in this list will be ignored (i.e. their crashes will -not be handled by .I abrt -). +will ignore packages in this list and will not handle their crashes. .TP .B EnabledPlugins = \fIplugin\fP, \fIplugin\fP ... -Only plugins in EnabledPlugins are loaded. +.I abrt +will only load plugins in this list. .TP .B Database = \fIdatabasePlugin\fP -This specifies which database plugin is used to store -the metadata about the crash. +This specifies which database plugin +.I abrt +uses to store metadata about the crash. .TP .B MaxCrashReportsSize = \fInumber\fP -You can specify here, how much disk space will maximally be -used for all the crash dumps, to ensure -that the crash dumps won't take -all the HDD space. The number is specified in megabytes. +The maximum disk space (specified in megabytes) that +.I abrt +will use for all the crash dumps. Specify a value here to ensure +that the crash dumps will not fill all available storage space. .TP .B ActionsAndReporters = \fIplugin\fP, \fIplugin(parameters)\fP -List of reporter and action plugins, which will be +List of reporter and action plugins which will be run at crash time. .SS [ AnalyzerActionsAndReporters ] This section contains associations between analyzers and action or reporter plugins. .TP .B CCpp = \fIplugin\fP -This plugin will be used when a C/C++ program crashes. +.I abrt +will use this plugin when a C/C++ program crashes. You can specify a plugin for specific program, for example .br CCpp:bind = Mailx("[abrt] Bind crashed") .br -The Mailx plugin will run, when bind crashes, instead of the plugin specified for +The Mailx plugin will run when bind crashes, instead of the plugin specified for all the C/C++ programs. .TP .B Kerneloops = \fIplugin\fP This plugin will be used in the case of kernel crashes. .SS [ Cron ] -This section specifies tasks, which will be run at some time. You can specify -either a time of the day in the format +This section specifies tasks that will be run at some specified time. You can specify +either a time of day in the format .br .B hh:mm = \fIplugin\fP .br |