Re: unlink()'s not quite POSIX behavior.

Joe Smith wrote: When the file's link count becomes 0 and no process has the file open, the space occupied by the file shall be freed and the file shall no longer Could we at least simulate the behavior by moving the file out of the way (simultaionsly renaming it to something unique), and forci

Re: unlink()'s not quite POSIX behavior.

"Joe Smith" wrote in message news:[EMAIL PROTECTED] Nevermind. I see that the relavent changes to NT_unlink are just very recent, and the only problem is that the latest cygwin dll does not incldue those changes yet. You can ignore the previous message. -- Unsubscribe info: http://cy

unlink()'s not quite POSIX behavior.

It appears that currently unlink will not immedately remove a file (that has only one link) if a handle to the file is open, but will flag it for deletion once the file handle closes. This is causing a problem with Python 3000. POSIX says: When the file's link count becomes 0 and no process