From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Checking for audit_enabled in the kernel Date: Tue, 14 Nov 2006 14:07:59 -0500 Message-ID: <200611141407.59544.sgrubb@redhat.com> References: <455A0157.9060100@hp.com> <200611141401.48925.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from discovery.boston.redhat.com (discovery.boston.redhat.com [172.16.80.171]) by mail.boston.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id kAEJ7YOY003275 for ; Tue, 14 Nov 2006 14:07:34 -0500 In-Reply-To: <200611141401.48925.sgrubb@redhat.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 List-Id: linux-audit@redhat.com On Tuesday 14 November 2006 14:01, Steve Grubb wrote: > A good example of how to do this is in audit.h: Actually, this is wrong - disregard. This would be modeled more like sending a user space rule into the kernel. In that case, audit_enabled is checked directly. Its already a public variable but just not in the audit.h file to prevent its proliferation. You can do this: extern int audit_enabled; in your file and use it. -Steve