'\" t .\" Title: audit_core_dumps .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: January 2017 .\" Manual: Audit Interfaces .\" Source: Kernel Hackers Manual 4.8.15 .\" Language: English .\" .TH "AUDIT_CORE_DUMPS" "9" "January 2017" "Kernel Hackers Manual 4\&.8\&." "Audit Interfaces" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" audit_core_dumps \- record information about processes that end abnormally .SH "SYNOPSIS" .HP \w'void\ audit_core_dumps('u .BI "void audit_core_dumps(long\ " "signr" ");" .SH "ARGUMENTS" .PP \fIsignr\fR .RS 4 signal value .RE .SH "DESCRIPTION" .PP If a process ends with a core dump, something fishy is going on and we should record the event for investigation\&. .SH "COPYRIGHT" .br