Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Message-ID: <ba40711f05051215544755b4e2@mail.gmail.com>
Date: Thu, 12 May 2005 18:54:28 -0400
From: Lev Bishop <lev DOT bishop AT gmail DOT com>
Reply-To: Lev Bishop <lev DOT bishop AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: tail -f and pipes with bash shell
In-Reply-To: <90459864DAD67D43BDD3D517DEFC2F7D05AF1E@axon.Axentia.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <90459864DAD67D43BDD3D517DEFC2F7D05AF1E AT axon DOT Axentia DOT local>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j4CMsgAq024115

On 11/05/05, Peter Ekberg <peda AT axentia DOT se> wrote:
> What is going on here?

My guess: "tail frame.log" closes its stdout as soon as it has read
the requested lines from the file, "tail -f frame.log" keeps its
stdout open, since it is waiting for new lines to be added to the
logfile. Cat is using some buffering on its stdin, so it tries to read
a buffer's worth of data at a time.

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