unlink() patch (was Cygwin CVS breaks PostgreSQL drop table)
Wed Jul 18 05:44:00 GMT 2001
On Wed, Jul 18, 2001 at 08:18:27AM -0600, Earnie Boyd wrote:
> 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.
I just realized that this question has to be combined with another
Is anybody aware of an application which would really miserably
fail if unlink() returns EBUSY? Besides `rm' of course ;-)
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:firstname.lastname@example.org
Red Hat, Inc.
More information about the Cygwin-patches