From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: PATH records show fcaps Date: Mon, 20 Oct 2008 18:52:40 -0400 Message-ID: <200810201852.40308.sgrubb@redhat.com> References: <1224343392.3189.74.camel@paris-laptop> <20081020163104.GA21901@us.ibm.com> <1224521741.3189.100.camel@paris-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1224521741.3189.100.camel@paris-laptop> 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: Eric Paris Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Monday 20 October 2008 12:55:41 Eric Paris wrote: > > Steve's suggestion of cap_prm and cap_inh are good for being shorter = and > > matching proc output. =C2=A0But OTOH it's a bit confusing as at first= I > > thought these were the task's values. =C2=A0Would it be too terse to = just > > use fP and fI? > > yes, too terse. How about cap_fP, cap_fI, cap_fVer, cap_fEffBit ? > > Based on your other comments I'm going to go add fVer and fEffBit. We don't have any audit fields with mixed cases in the field name. Let's = not=20 start it so that searches stay simple. Thanks, -Steve