Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: Date: Thu, 12 May 2005 18:54:28 -0400 From: Lev Bishop Reply-To: Lev Bishop To: cygwin@cygwin.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@axon.Axentia.local> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j4CMsgAq024115 On 11/05/05, Peter Ekberg 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/