Date: Fri, 27 Nov 2009 01:20:50 +0100
To: cygwin AT cygwin DOT com
Subject: Re: tar hangs on unpacking calcoo_1.3.16.orig.tar
Message-ID: <20091127002050.GA27305@win.tue.nl>
References: <5a05e0e60911261052w2e60586cxe7a90d02b4cf6e0f AT mail DOT gmail DOT com> <20091126213025 DOT GA26443 AT win DOT tue DOT nl> <4B0EF59B DOT 90609 AT cs DOT umass DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B0EF59B.90609@cs.umass.edu>
User-Agent: Mutt/1.5.18 (2008-05-17)
From: rp AT win DOT tue DOT nl (Reinier Post)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Thu, Nov 26, 2009 at 04:39:39PM -0500, Eliot Moss wrote:
> I wonder if some process has created the file in
> question and still has it open. Then a call to
> create, and a call to unlink, will both fail.

But the call to open is failing (the fd returned is -1),
which is why the unlink() is executed in the first place,
and it does *not* fail.

My vote for Stephan Mueller's suggestion that the 'aux' in the
name is causing the problem - but this still doesn't explaing why
the unlink() claims to succeed (returning 0); the loop within tar
should be changed to deal with this situation in any case.
Not sure how.

Thanks for your suggestions.

(I'm running the same script on Linux now, if only
 because it's running more than 100 times as fast there.
 But that has nothing to do with tar bugs.)

-- 
Reinier Post
TU Eindhoven

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