From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [PATCH] Rework of IPC auditing Date: Fri, 31 Mar 2006 14:24:44 -0500 Message-ID: <200603311424.44064.sgrubb@redhat.com> References: <1142018719.13416.91.camel@kirkland1.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1142018719.13416.91.camel@kirkland1.austin.ibm.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com, dustin.kirkland@us.ibm.com List-Id: linux-audit@redhat.com On Friday 10 March 2006 14:25, Dustin Kirkland wrote: > 2) Support for an AUDIT_IPC_NEW_PERM audit message type. =C2=A0This all= ows > for separate auxiliary audit records for normal operations on an IPC > object and permissions changes. =C2=A0Note that the same struct > audit_aux_data_ipcctl is used and populated, however there are separate > audit_log_format statements based on the type of the message. Can we have another name for this record type? I don't want us to get in = the=20 habit of adding "new" to the record type name. Is there something that be= tter=20 describes its purpose? -Steve