Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
X-Authentication-Warning: modi.xraylith.wisc.edu: khan owned process doing -bs
Date: Tue, 27 Apr 1999 16:01:23 -0500 (CDT)
From: Mumit Khan <khan AT xraylith DOT wisc DOT edu>
To: thomas AT on DOT com
cc: gnu-win32 AT cygnus DOT com
Subject: Re: tail -f <file name> locks <file name>
In-Reply-To: <85256760.006A2422.00@mail.on.com>
Message-ID: <Pine.SUN.3.93.990427155056.22463B-100000@modi.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 27 Apr 1999 thomas AT on DOT com wrote:

> This has not been the original intention of 'tail -f': This command should
> enable the user
> to watch the contents of a file grow. If this file is locked by the tail
> command, the writing process
> will run on error.
> 

I'm not sure why you're seeing a problem, but I do the following all the
time:
  
  $ make > make.log 2>&1 &
  $ tail -f make.log

And in some cases, the ``tail -f make.log'' is already running in a
different window when I issue the ``make'' command.

Is the writer explicitly locking the output file? Could you show an 
example of the failure? 

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com