This is the mail archive of the
cygwin-patches@cygwin.com
mailing list for the Cygwin project.
Re: unlink() patch (was Cygwin CVS breaks PostgreSQL drop table)
- To: Corinna Vinschen <cygwin-patches at cygwin dot com>
- Subject: Re: unlink() patch (was Cygwin CVS breaks PostgreSQL drop table)
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Wed, 18 Jul 2001 08:18:27 -0600
- CC: Cygwin-Patches <cygwin-patches at sources dot redhat dot com>
- References: <20010717221042.A426@dothill.com> <20010718130154.E730@cygbert.vinschen.de>
- Reply-To: CP List <Cygwin-Patches at Cygwin dot Com>
Corinna Vinschen wrote:
>
> BTW, I have a naive question related to unlink. I had just another
> look into SUSv2 and to my surprise it defines the following error
> code:
>
> [EBUSY] The file named by the path argument cannot be unlinked
> because it is being used by the system or another process
> and the implementation considers this an error.
>
> which basically means, if we try to unlink a file and that fails,
> we wouldn't have to force it by ugly tricks (delqueue) but just
> return EBUSY and Cygwin would still be SUSv2 compliant.
>
> All: Would that be ok to change or would you like to keep the current
> behaviour?
>
I vote for EBUSY. The delqueue has the potential to be more harmful
than good.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com