Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040518123138.032783b0@127.0.0.1> X-Sender: Date: Tue, 18 May 2004 12:35:09 -0400 To: C Wells , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: tail and win file handling In-Reply-To: <20040518133131.60389.qmail@web60408.mail.yahoo.com> References: <20040518131630 DOT GZ12030 AT cygbert DOT vinschen DOT de> <20040518133131 DOT 60389 DOT qmail AT web60408 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 09:31 AM 5/18/2004, you wrote: >I am sorry if this has been covered before, but I was >wondering if there is work around (probably not ;-( > >In unix you can do the following >tail -f /somefile >in another session >rm -f /somefile >echo OK > /somefile > >of course the tail stops working, but the file is >recreated > >On a cygwin box >tail -f c:/somefile >in another session >rm -f c:/somefile >echo OK > c:/somefile >'Access is denied' > >So obviously the tail puts a lock on the file, >preventing an application from creating a new one, >which in my case breaks the application. Any thoughts >about how work around this, given I need to tail the >file ? Your going to have to use a different file name. Windows doesn't support the same semantics in this case. The emulation Cygwin provides is as close as you're going to get (which ain't that close but... ;-) ). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/