From mboxrd@z Thu Jan 1 00:00:00 1970 From: LC Bruzenak Subject: Re: ausearch nodes option Date: Fri, 05 Jun 2009 10:12:30 -0500 Message-ID: <1244214750.31664.519.camel@homeserver> References: <1244210822.31664.515.camel@homeserver> <200906051042.19485.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200906051042.19485.sgrubb@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Steve Grubb Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Fri, 2009-06-05 at 10:42 -0400, Steve Grubb wrote: > On Friday 05 June 2009 10:07:02 am LC Bruzenak wrote: > > In an ausearch I would like to look for events from multiple hosts. > > Ideally I would have multiple "-n " entries which would return > > events for any of the hosts. > > > > The man page says that the options form an "and" statement. I find this > > isn't the case with multiple hosts specified, but the result is the > > "last host listed wins": > > ausearch has one and exactly one entry for each search option that you add to > a command line. Two nodes don't work just as two files or two terminals don't > work. It does however do a partial match. So you could have a naming scheme > that allows search by subnet. > > ausearch -n 192.168.1 OK; thanks. This will not help me though, since the collector has multiple NICs on different subnets and the hosts I need to extract are all on different ones. So I end up with the same situation there. > > > > I may patch my own ausearch to behave differently. > > If you patch yours, send it to the list. Will do. LCB. -- LC (Lenny) Bruzenak lenny@magitekltd.com