| Server IP : 67.43.7.42 / Your IP : 216.73.216.61 Web Server : Apache System : Linux host.isabellascookies.com 2.6.32-754.35.1.el6.x86_64 #1 SMP Sat Nov 7 12:42:14 UTC 2020 x86_64 User : isabella ( 503) PHP Version : 5.5.38 Disable Function : exec,passthru,shell_exec,system MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /etc/libreport/ |
Upload File : |
# This configuration file specifies which programs should be run # when the specified event occurs in problem directory lifetime. # # It consists of directives and rules. # # Directives start with a reserved word. Currently, there is only one # directive, "include". Its format is "include FILE". # It causes files which match FILE to be read and # parsed as if they are inserted textually where this directive # occurs. FILE can use shell pattern metacharacters (*,?,etc) to # specify multiple files. Relative paths are interpreted relative # to current file. # # Rule starts with a line with non-space leading character. # All subsequent lines which start with space or tab form one rule. # Note that separating newline is *retained*. Example: # EVENT=post-create date >/tmp/dt # semicolon is not needed here! # echo $HOSTNAME `uname -r` # # Rules may be commented out with #. One # is sufficient to comment out # even a multi-line rule (no need to comment out every line). # # Rules specify which programs to run on the problem directory. # Each rule may have conditions to be checked before the program is run. # # Conditions have form VAR=VAL or VAL~=REGEX, where VAR is either # word "EVENT" or a name of problem directory element to be checked # (for example, "executable", "package", hostname" etc). # # If all conditions match, the remaining part of the rule # (the "program" part) is run in the shell. # All shell language constructs are valid. # All stdout and stderr output is captured and passed to abrt # and possibly to abrt's frontends and shown to the user. # # If the program terminates with nonzero exit code, # the event processing is considered unsuccessful and is stopped. # Last captured output line, if any, is considered to be # the error message indicating the reason of the failure, # and may be used by abrt as such. # # If the program terminates successfully, next rule is read # and processed. This process is repeated until the end of this file. include events.d/*.conf # For testing purposes only #EVENT=report_Dummy analyzer=libreport echo "Hello world" >> /tmp/libreport.log