Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
From:	"Blair P. Houghton" <blair AT houghton DOT net>
Subject:	unlink(2) or fopen(3) failing under cygwin
Date:	Tue, 23 Mar 2004 16:44:41 +0000 (UTC)
Lines:	19
Message-ID:	<loom.20040323T173940-810@post.gmane.org>
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	main.gmane.org
User-Agent:	Loom/3.14 (http://gmane.org/)
X-Loom-IP:	12.2.142.7 (Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1))

I forget.  What's the command to dump the system config?

Here's what `uname -a' says:

    CYGWIN_NT-5.1 eMachine64-3000 1.5.7(0.109/3/2) \ 
2004-01-30 19:32 i686 unknown unknown Cygwin

unlink(2) seems to be causing a subsequent fopen(3)
to fail.  Originally, it was the unlink call that
failed, but putting it in a loop

    while(!unlink(...))

made it work.

Does anyone know of any reason an fopen on the
just-unlinked file would fail under Cygwin?

--Blair


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

- Raw text -