MIME-Version: 1.0
In-Reply-To: <4AC4E962.8020307@gmail.com>
References: <274475.31177.qm@web30806.mail.mud.yahoo.com> 	 <4AC4E962.8020307@gmail.com>
Date: Thu, 1 Oct 2009 13:45:19 -0400
Message-ID: <b0ddfae80910011045ycb6c5aexa630e6feafe6cff@mail.gmail.com>
Subject: Re: Assistance sought grepping log files
From: mike marchywka <marchywka@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Thu, Oct 1, 2009 at 1:39 PM, Dave Korn
<dave.korn.cygwin@googlemail.com> wrote:
> 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) i=
nto
>> 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 ju=
st
>> fine.
>
> =A0You could use the "od" utility to see what's actually going on in these
> files. =A0My guess would be that there are embedded ascii NULs that are c=
ausing
> all the string processing routines in awk/grep etc. to fail. =A0If that's=
 the
> case, running them through "tr -d '\0'" might help.
>
It sounds like he may be unfamiliar with regex but yes it could be unicode =
or
something. if you see zero every other character that will be apparent.


--

--
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