Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Scott Alexander" <salexander AT tepik DOT com>
To: "Cygwin" <cygwin AT sources DOT redhat DOT com>
Subject: RE: tail -f problem
Date: Fri, 31 Jan 2003 14:20:04 -0800
Message-ID: <FNECLMPOECFEEEOLCOMPMEBLCDAA.salexander@tepik.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <005601c2c957$f76033d0$050a10ac@bluesguitar.org>

I've read the archives (now that I found it) about other people posting
about this.  However, this does not change the fact that linux's version of
tail works plenty fine with viewing IIS logfiles vs. Cygwin's version of
tail.

-----Original Message-----
From: Matthew Smith [mailto:matts AT bluesguitar DOT org]
Sent: Friday, January 31, 2003 10:39 AM
To: Cygwin
Cc: Scott Alexander
Subject: Re: tail -f problem


This is not the fault of tail, rather IIS.  Search the archives if you're
interested why.

cheers,
-Matt Smith



> With cygwin's tail, the output is not quite the same as the linux version
of
> tail.  With Cygwin's version, I will get output with tail -f, but the
> updates aren't "realtime" as the linux version -- the updates are barely
> shown at all, if ever.  Here are the different methods I used to try and
> parse the IIS log file:
> Thanks,
> -Scott



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/