On Nov 26 19:52, Christopher Faylor wrote: > On Fri, Nov 27, 2009 at 01:20:50AM +0100, Reinier Post wrote: > >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. > > No, it shouldn't. We are not going to patch every conceivable > program to understand MS-DOS special files. > > This won't be a problem with Cygwin 1.7. If you want a fix change > to that.
Just as a sidenote a pointer to the new User's Guide: http://cygwin.com/1.7/cygwin-ug-net/using-specialnames.html#pathnames-dosdevices Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
