Date: Fri, 20 Mar 2009 20:09:21 +0100
From: Spiro Trikaliotis <an-cygwin@spiro.trikaliotis.net>
To: cygwin@cygwin.com
Message-ID: <20090320190921.GM6141@trikaliotis.net>
Mail-Followup-To: cygwin@cygwin.com
References: <49C3BF14.5000602@bull.net> <49C3E438.4070301@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49C3E438.4070301@gmail.com>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
Subject: Re: UNLINK problem (again!!)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Hello,

* On Fri, Mar 20, 2009 at 06:45:12PM +0000 Dave Korn wrote:
 
>   This is Cygwin correctly implementing the POSIX "can delete a file while
> retaining a handle to its contents" semantic, followed by the known Cygwin
> problem (a restiction of the underlying windows OS) that you can't (as you can
> in POSIX) create a new file in place of the old one while you keep that handle
> to the old one's contents.

This restriction could be solved by renaming the file before deleting
it.

The only problem I see with this approach: What file name to choose for
the rename operation?

Best regards,
Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/

--
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/