Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

reporter-mailx(1) [centos man page]

REPORTER-MAILX(1)						 LIBREPORT MANUAL						 REPORTER-MAILX(1)

NAME
reporter-mailx - Sends contents of a problem directory via email. SYNOPSIS
reporter-mailx [-v] -d DIR [-c CONFFILE] DESCRIPTION
The tool reads a problem directory, composes an email message from the directory contents, and uses mailx to send the message to specified recipient. Properties of email messages can be specified in a configuration file, and via environment variables. Configuration file Configuration file contains entries in a format "Option = Value". The options are: Subject The subject of the email message. EmailFrom The sender of the email message. EmailTo The recipient of the email message. SendBinaryData Use yes/true/on/1 to attach all binary files from the problem directory to the email. This can cause the emails to be very large. Integration with ABRT events reporter-mailx can be used as a reporter, to allow users report problems via email when they decide to do it. This usage is pre-configured in /etc/libreport/events.d/mailx_event.conf: EVENT=report_Mailx reporter-mailx It can also be used to notify administrator automatically when a problem happens. When this is desired, modify the event configuration file to run the tool on the post-create event: EVENT=post-create reporter-mailx OPTIONS
-d DIR Path to problem directory. -c CONFFILE Path to configuration file. When used in ABRT event system, the file contains site-wide configuration. Users can change the values via environment variables. ENVIRONMENT VARIABLES
Environment variables take precedence over values provided in the configuration file. Mailx_Subject Subject of the email message. Mailx_EmailFrom Sender of the email message. Mailx_EmailTo Recipient of the email message. If nor the environment variable nor the corresponding option is defined, the message is send to "root@localhost". Mailx_SendBinaryData Use yes/true/on/1 to attach all binary files from the problem directory to the email. AUTHORS
o ABRT team LIBREPORT 2.1.11 06/18/2014 REPORTER-MAILX(1)

Check Out this Related Man Page

REPORT-GTK(1)							 LIBREPORT MANUAL						     REPORT-GTK(1)

NAME
report-gtk - GUI tool to analyze and report ABRT problems SYNOPSIS
report-gtk [-vpdx] [-e EVENT] [-g GUI_FILE] PROBLEM_DIR DESCRIPTION
report-gtk is a graphical tool that reports application crashes and other problems caught by abrtd daemon, or created by other programs using libreport. report-gtk works with a single problem saved in specified PROBLEM_DIR. In the expert mode it enables access to and manipulation of problem data. OPTIONS
-d, --delete Remove PROBLEM_DIR after reporting -e EVENT Run only theset EVENTs on PROBLEM_DIR -g FILE Alternate GUI file -p Add program names to log -v, --verbose Be verbose -V, --version Display version and exit -x, --expert Enabled advanced features CONFIGURATION
Reporting work flow configuration These configuration files are placed in /usr/share/libreport/workflows. Each file has XML formatting with the following DTD: <!ELEMENT workflow (name+,description+,events*)> <!ELEMENT name (#PCDATA)> <!ATTLIST name xml:lang CDATA #IMPLIED> <!ELEMENT description (#PCDATA)> <!ATTLIST description xml:lang CDATA #IMPLIED> <!ELEMENT events = (event)+> <!ELEMENT event = (#PCDATA)> name User visible name description User visible description events List of executed events event Name of event. If event is not applicable on the problem data or if it is not defined then process continues with next event sibling. EXAMPLES
Simple reporting work flow <workflow> <name xml:lang="en">Example</name> <name xml:lang="cs">Piklad</name> <description xml:lang="en">Example description</description> <description xml:lang="cs">Piklad popisu</description> <evetns> <event>analyze_example</event> <event>collect_example</event> <event>report_example</event> </events> </workflow> AUTHORS
o ABRT team LIBREPORT 2.1.11 06/18/2014 REPORT-GTK(1)
Man Page