From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Exclude /usr/libexec/mysqld from audit.rules Date: Mon, 09 Dec 2013 10:34:19 -0500 Message-ID: <10198302.85ZcV1VRhC@x2> References: <22012185.RRsLhnfhFh@x2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Derek Warner Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Monday, December 09, 2013 10:20:41 AM Derek Warner wrote: > How did you "interpret" the log setting to retreive the syscall > "sched_setparam"? I copied the text and ran it through ausearch with the '-i' commandline option. > Anyhow I am not sure why we want this, I have no idea what the > sched_setparam actually does. It changes the priority of the process. Which is not exactly security critical. For concerns in this area, one would generally set rlimits to prevent a resource hog. Additionally, if you really, really wanted to see this, you'd only want the ones that succeed or fail due to EPERM. >Did you do a lookup on the mysql syscall number? No, I used the audit tools to check it. -Steve