From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: user showing up as unset Date: Wed, 11 May 2011 10:37:54 -0400 Message-ID: <201105111037.55130.sgrubb@redhat.com> References: <4D8348804BD0AE4EB58593EA9539CFF5A192F6@es-22b.manassas.progeny.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D8348804BD0AE4EB58593EA9539CFF5A192F6@es-22b.manassas.progeny.net> 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 Cc: "Harris, Todd" List-Id: linux-audit@redhat.com On Monday, May 09, 2011 03:47:39 PM Harris, Todd wrote: > So I was wondering if anyone had seen this. I have a set of nodes that > when we setup auditd on them the events we get back list the auid as > unset for basically everything except for login which shows up > correctly. Does anyone know where I may need to look at the config, > something in PAM or else where? All entry point daemons should have a call to pam_loginuid in their pam stack. This would be login, sshd, gdm, kdm, xdm, vsftpd, cron, etc. You might also want audit=1 added to the kernel boot line. -Steve