Message-ID: <4AC4E962.8020307@gmail.com>
Date: Thu, 01 Oct 2009 18:39:46 +0100
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Assistance sought grepping log files
References: <274475.31177.qm@web30806.mail.mud.yahoo.com>
In-Reply-To: <274475.31177.qm@web30806.mail.mud.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Larry W. Virden wrote:

> For example, I've copied some of the "12 hive" tracing logs from IIS (or
> maybe it is SharePoint... I'm still struggling to figure all this out) into
> a directory to which I have access.
> 
> Now I'd like to crunch those logs to see the errors, etc.
> 
> awk and grep, however, do not seem to find anything in the files.

> The weird thing is that when I use the "more" command, the file looks just
> fine.

  You could use the "od" utility to see what's actually going on in these
files.  My guess would be that there are embedded ascii NULs that are causing
all the string processing routines in awk/grep etc. to fail.  If that's the
case, running them through "tr -d '\0'" might help.

    cheers,
      DaveK

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple