On 11/26/2009 04:30 PM, Reinier Post wrote:
Dear list,
I've been using Cygwin daily for years and I'm very happy with it.
But today it threw a nice puzzle at me. I must confess I became
a list member just to report it.
...
Please don't commandeer another's email thread for your own purpose
On Fri, Nov 27, 2009 at 03:06:50PM +, Dave Korn wrote:
[...]
> It's certainly a bug that unlink() returns 0 on a file that doesn't exist,
> instead of indicating ENOENT. However 1.5 series is dead, there aren't going
> to be any further updates to it. You can always get the sources and pa
Reinier Post wrote:
> On Fri, Nov 27, 2009 at 09:56:08AM +0100, Corinna Vinschen wrote:
>>> No, it shouldn't. We are not going to patch every conceivable
>>> program to understand MS-DOS special files.
>
> I am not asking for tar to deal with a special file,
> but with a C source code file that
For my part, I can confirm that file names
aux and aux.c work fine when created by
touch or by > from bash ... in cygwin
1.7.0-65 under Windows 7.
Best wishes -- EM
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http
On Fri, Nov 27, 2009 at 09:56:08AM +0100, Corinna Vinschen wrote:
> 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
>
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
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 i
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 exec
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.
You might not see the file until the process
closes it or dies ...
Just a wondering ...
The procexp tool from sysinternals.com might
reveal an open file
Reinier Post writes:
" curl
ftp://ftp.debian.org/debian/pool/main/c/calcoo/calcoo_1.3.16.orig.tar.gz
" | tar zxvf -
"
" hangs after printing the line
"
" calcoo-1.3.16/src/aux.c
"
" This happens on two different i386 systems, both running an up to date Cygwin
" on an up to date Windows XP with
Dear list,
I've been using Cygwin daily for years and I'm very happy with it.
But today it threw a nice puzzle at me. I must confess I became
a list member just to report it.
My Cygwin /usr/bin/tar hangs when unpacking an archive:
curl ftp://ftp.debian.org/debian/pool/main/c/calcoo/calcoo_1
11 matches
Mail list logo
