To: cygwin@cygwin.com
From: Jean-Pierre Bergamin <james@ractive.ch>
Subject: Re: less locks the file
Date: Tue, 21 Jun 2011 12:03:49 +0200
Lines: 27
Message-ID: <itpqde$uf9$1@dough.gmane.org>
References: <itpij1$foc$1@dough.gmane.org> <20110621081809.GO3437@calimero.vinschen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
In-Reply-To: <20110621081809.GO3437@calimero.vinschen.de>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Am 21.06.2011 10:18, schrieb Corinna Vinschen:
> On Jun 21 09:50, Jean-Pierre Bergamin wrote:
>> Dear cygwin-Users
>>
>> When using less to follow a log file (less +F logfile.log), this
>> file is locked. So when I restart the application, it cannot delete
>> this locked log file and create a new one. So I always have to quit
>> less, before restarting the app, which I of course forget like every
>> 2nd time... less does not lock on linux.
>>
>> Is there any way I could tell less not to lock the file?
>
> Upgrade Cygwin to the latest release might be an option.  It's not less
> which locks the file, it's the fact that Windows does not allow to
> delete files which are in use.  Recent Cygwin versions have a workaround
> for this.

Unfortunately, it also does not work with the latest cygwin version.
It seems to be some "special" behaviour with my app server anyway, since 
I can open any other file with less and delete it and recreate it, while 
less still has it open. No idea why the app server (virgo) fails.

But thanks anyway.


Best regards,
James


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