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 From: "Hannu E K Nevalainen" To: Subject: RE: unlink(2) or fopen(3) failing under cygwin Date: Tue, 23 Mar 2004 19:51:39 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: > -----Original Message----- > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf > Of Blair P.Houghton > Sent: Tuesday, March 23, 2004 5:45 PM > To: cygwin AT cygwin DOT com > Subject: unlink(2) or fopen(3) failing under cygwin > > > 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? IIRC this has been up earlier; unlink() isn't atomic. Search the archives: google("site:cygwin.com inurl:ml +atomic +unlink") might be a good start I guess. /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E ** on a mailing list; please keep replies on that particular list ** -- printf("LocalTime: UTC+%02d\n",(DST)? 2:1); -- --END OF MESSAGE-- -- 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/